Things Every Programmer Should Know

Re:Things Every Programmer Should Know by ryanbrush on Friday September 20, 2013 @09:19AM (#6417487)

Using that cache is a good idea. The site linked to was used to gather the original content rather than broad consumption. (I wrote two of the chapters in this book, and this was where we revised them.)

Lots of good articles in there, though.

[ Parent | on HN ]

Re:Things Every Programmer Should Know by JeremyMorgan on Friday September 20, 2013 @10:04AM (#6417734)

Nice work Ryan. I've been reading through these, and "Code is Design" is roughly similar to something I was trying to explain to my manager not too long ago, but I couldn't quite put it into words. I just sent him a link haha.

The parallels between software and physical construction are pretty amazing.

[ Parent | on HN ]

Re:Things Every Programmer Should Know by jefffoster on Friday September 20, 2013 @02:28PM (#6419587)

Jack Reeves essays on software design are also worth a read http://www.developerdotstar.com/mag/articles/reeves_design_m...

[ Parent | on HN ]

Re:Things Every Programmer Should Know by ryanbrush on Friday September 20, 2013 @10:06PM (#6421675)

Yes, these are excellent, and goes into much more depth than the brief article I wrote.

[ Parent | on HN ]

Re:Things Every Programmer Should Know by ryanbrush on Friday September 20, 2013 @10:06PM (#6421673)

Very kind of you to say! I came up with the metaphor when needing to explain this to a semi-technical person as well, so we've had similar needs there.

[ Parent | on HN ]