I wouldn't trust/believe a programmer who isn't ashamed of something they've done. In an embedded system, I couldn't think of a nice way to check for the start+end dates for daylight savings time, so I just hard-coded…
I mixed up the meanings of "debit" and "credit", and wrote a credit card processing app that ended up PAYING $75K to our customers instead of charging them. I'm still not sure how this bug slipped past the bank's tough…
My prob wasn't really about being lost in parenthesis; I had an editor with bracket matching. My prob was the "inside-out" thinking that LISP requires. It's tricky when you're coming from a BASIC/PASCAL/C background.…
I got great grades in college, but could never wrap my head around LISP (Lost In Stupid Parentheses). For anything non-trivial, I cheated and handed in somebody else's work. There, I said it.
Yay, I don't have to use ctrl-K codes like the original TP3 editor!
I wouldn't trust/believe a programmer who isn't ashamed of something they've done. In an embedded system, I couldn't think of a nice way to check for the start+end dates for daylight savings time, so I just hard-coded…
I mixed up the meanings of "debit" and "credit", and wrote a credit card processing app that ended up PAYING $75K to our customers instead of charging them. I'm still not sure how this bug slipped past the bank's tough…
My prob wasn't really about being lost in parenthesis; I had an editor with bracket matching. My prob was the "inside-out" thinking that LISP requires. It's tricky when you're coming from a BASIC/PASCAL/C background.…
I got great grades in college, but could never wrap my head around LISP (Lost In Stupid Parentheses). For anything non-trivial, I cheated and handed in somebody else's work. There, I said it.
Yay, I don't have to use ctrl-K codes like the original TP3 editor!