Coding for Humans

re: Coding for Humans

SteveRowe — Fri, 29 Jun 2007 03:32:32 GMT

@Hiren - no, I haven't read that one yet. I have read some of "Smalltalk Best Practice Patterns" by Kent Beck which seems to cover similar ground.

The Rules of Code Optimization

Ryan Bemrose — Tue, 19 Jun 2007 19:41:08 GMT

Pingback from http://blogs.msdn.com/audiofool/archive/2007/06/14/the-rules-of-code-optimization.aspx

(Don't know why these things aren't automatic anymore)

re: Coding for Humans

Hiren (hithacker@gmail.com) — Tue, 19 Jun 2007 13:19:29 GMT

have u read book Smalltalk With Style ? if not please download it from www.iam.unibe.ch/ducasse/FreeBooks.html and read.

It is collection of pragmatic tips for Smalltalk.

re: Coding for Humans

Mark Sowul — Wed, 13 Jun 2007 06:46:15 GMT

Amen, I had noticed that on enough of my own projects where I come back to something later that is done in a non-obvious way, not necessarily for performance or whatnot, but to work around a bug, and helpfully say to myself, "What a stupid way to do things, what's wrong with me" and change it to the 'normal' way only to find (or not find, or find out much later) that there was a reason for it. So now I make sure to document why things are the way they are and comment out code with a reason rather than just removing it wholesale.

I now take the same principle to others' code, which is that, even if it's not well-documented, that other developers are not stupid, and that there's a reason they wrote it like they did (within reason). I guess it's similar to Raymond's psychic debugging tip: when seeing unfamiliar code, assume it's mostly correct (http://blogs.msdn.com/oldnewthing/archive/2007/04/23/2215961.aspx)

re: Coding for Humans

Merrion — Tue, 12 Jun 2007 11:36:15 GMT

New hires should get a copy of "Code Complete" on their desk when they come in - it goes a long way to helping them understand the need for maintenance in code.