kirkthejerk

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 arrays with 10 years worth of dates.

I was eventually surprised to find out that (A) in 2005 the US changed the DST dates, and (B) our system actually survived longer than ten years.

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 app certification process, though.

Traipsing around botanical gardens with my laptop sounds divine, but what if I need (yes, need) a multi-monitor PC and wired network?

If adjustable sitting/standing desks are all the rage nowadays, how about cubicle walls that raise/lower (all the way to the ceiling)? Scrum time? Lower the walls. Need a bit of quiet contemplation? Shields up!

I'll bet that somebody with better time/money/smarts/connections/looks/luck/location than me could get funding for this invention ;)

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'm a sucker for punishment, so after my first (bad) taste of LISP, I took an AI course that was 100% LISP. My AI teacher studied under McCarthy at Stanford, so I probably can't blame him for anything.

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!