News for hackers. Stuff that matters.
Re:I've never seen a language's style guide recommend avoidi... by commandar on Wednesday July 23, 2014 @09:23AM (#8074206)
I'm in a field (healthcare integration) where vendors constantly break spec or handle things in a quirky manner.

The actual code I work with is fairly straightforward and easy to understand functionally. I can understand the what of pretty much any of the code my organization runs in short order.

But the why is vital. This week I've implemented things for reasons I won't remember in six months. Simple, easy to understand code. I've also been fighting with another system that predates me. I can see that it's modifying the original message to map particular values elsewhere downstream, but I have absolutely no idea why or which downstream system is expecting them. I've lost hours trying to track this down when a line or two explaining WTF the piece of code exists would have told me exactly where I needed to look.

Yes, your code should be understandable and self documenting to some degree anyway. But your code doesn't exist in a vacuum, and can't document what exists external to it.

Re:I've never seen a language's style guide recommend avoidi... by remon on Friday July 25, 2014 @07:08AM (#8084596)
My sentiments exactly.