skatenerd

i wonder where in the world the "occupational hazard" number is highest, and what the number looks like

have you thought about attempting to accomplish these things in the evenings? once school is done and all that

I don't know much about interoperation between clojure and java, but wouldn't it make more sense to build a java gui which makes calls to some sort of clojure backend?

sounds like she might not have been confused if the bit to the right of the equals sign didn't contain an "X".

in other words, maybe it's not mutability that is confusing her.

...this isn't to say i'm not a huge fan of immutability :-)

I'm pretty excited to play The Dark Mod for free (http://www.thedarkmod.com/)

in my opinion, the issue is not at its root about being a good craftsman.

what ultimately matters to me is avoiding the painful/frustrating/stressful productivity crash that can occur when maintaining software.

software craftsmanship is a means to that end.

this is essentially in agreement with what the article said. i think its worth clarifying that there are things you are trying to avoid, and then certain practices are means to that end.

two things you might hear in this situation are "be entreprenurial with edge cases" and "if you write robust edge-case-ignorant code, the modifications later should be easy". It's not immediately obvious how to respond in these situations.

trying to work through things on your own before coding, the fifteen-minute clarification process can start looking like a few days. and there's also no guarantee that you'll think of everything.

as for writing code that doesn't break when you work in the edge case you hadn't thought of, well, i guess that comes with experience.

I thought it was legitimately worth pointing out that there is a popular post on hacker news that is about hacker news.

I apologize for inappropriately using a meme to make that point.

"sup dog"