Something I explained to Jessica today: It's possible to have code that works but that no one really understands. In fact, not just possible, but the default.
-
-
Definitely. I consider it a valuable hint on how to write better code. I don't know if this is just pre-meditating contexts, but it helps me think of how I'd come back to my code and what I'll change this time around.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
year? Can't understand the code I wrote 3 months ago. :(
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I had seen some code with descriptions like “damned if I know”. Engineers can be funny.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
In my first dev job, our client had a printer in the corner a server room. It filled a box each day with printouts that were taken directly to the trash. When I asked if we could just turn those off, I got laughed out of the room. No one had any idea what would break.
-
Hahaha, this is hilarious!
End of conversation
New conversation -
-
-
@paulg you should start programming in Ruby. - Show replies
New conversation -
-
-
100% - I almost always hate myself for the variable names I choose that, at the time, seemed to make sense, but objectively make no sense whatsoever.
-
I've noticed the variable 'joe' appears in the Zrankings codebase on occasion. This phenomenon is not exclusive to one contributor.
- Show replies
New conversation -
-
-
That applies to not all the code we write. I've got some pieces from several years ago which I can read, understand and, after a cup of coffee, even work on.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.