not sure if this is the right forum for this, but I just finished Dreaming in Code.http://www.dreamingincode.com/I thought it was pretty amusing and I like the intermissions into famous software books, quotes, and anecdotes. always have loved references to the mythical man month, but I have a feeling I shouldn't read it.anyone else read it? has anyone tried chandler? thoughts on why this is such a depressing story?
4/26/2009 11:00:29 AM
4/26/2009 12:51:38 PM
^I have a feeling it'd be out of date. I mean, it was published in 1975. that's pretty ancient for the industry. I find the basic ideas relevant of course, but I imagine the details would be uber boring.oh also, I just reread "getting real" by 37signals.I'm now convinced that the optimal team size is 1.
4/26/2009 3:45:56 PM
4/26/2009 3:54:14 PM
its 2
4/26/2009 4:25:56 PM
I thought this thread was literally going to be about dreaming in code, which I've done before.
4/27/2009 12:48:15 PM
for($i=1; $i <= 50000000000000; $i++){ boneJennaFisher;}
4/27/2009 12:57:07 PM
Read this last year - good read on exactly how *not* to run a software project. Chandler is an amazing pile of suck
4/27/2009 1:17:39 PM
4/28/2009 1:16:10 PM
i think the its 2 post was a joke
4/28/2009 1:31:50 PM
^exactly, because we all know the proper team size is 3 ... me, myself, and I.
4/28/2009 2:47:46 PM
Everyone knows the answer is 47.
4/28/2009 6:08:22 PM
another well known and excellent book in this genre is The Pragmatic Programmer by Andy Hunt (who lives in RTP apparently)He gave a talk in Charlotte tonight about his upcoming book Pragmatic Thinking and Learning: Refactor Your Wetware. very cool and interesting stuff
4/28/2009 9:29:52 PM