21–30 of 92 posts
I've found woodworking to be an incredible analogy (and also contrast) to software dev. The guy at http://woodgears.ca/ was formerly a software engineer, and I find it interesting how this influences he approaches woodworking.
There was a talk at Clojure/conj by Tim Ewald on just that: https://www.youtube.com/watch?v=ShEez0JkOFw "Programming with hand tools" Lots of conference reviews nominated it in their favourite talks too.
I was thinking of doing the exact opposite of this book, writing a book in C code that has to be compiled first.
Did you mean literate programming? Something like "A Retargetable C Compiler" maybe?
I was thinking more along the lines of IOCCC. No matter how unreadable the code is, if it compiles and runs without grievance, it is superior to most of the nonsensical, god-awful English seen on the web.
> Something like "A Retargetable C Compiler" maybe?
Shit - come back to me in ten years time, then I might be able to answer.
General subject is correct: the more code is pasted in the book - the lesser value it usually is. These 1,200 page overpriced heavy monsters in a bookstore are usually sheer waste of paper.
I am sorry, but for me that book was a no. It just felt like a self help book, but for programmers, which is kind of ok if you are feeling any sort of personal trouble in the field. Not that this is not already told on the back cover, but no, I would not call this book the best development book. I did not buy it, instead, it was the result of participating in a local dev Google something, but it really surprised me h…
I've found woodworking to be an incredible analogy (and also contrast) to software dev. The guy at http://woodgears.ca/ was formerly a software engineer, and I find it interesting how this influences he approaches woodworking.
There was a talk at Clojure/conj by Tim Ewald on just that: https://www.youtube.com/watch?v=ShEez0JkOFw "Programming with hand tools" Lots of conference reviews nominated it in their favourite talks too.
I found Apprenticeship Patterns to be a great book to read in your first few months working professionally (or during an internship). It's had a huge impact on me and is one of the three books I recommend to every new hire that I meet (the rest are here: http://mdswanson.com/blog/2013/05/31/summer-reading-list.htm... ). Some of my favorite sections: * The Long Road: keep your focus on the long term, value growth over…
best development book I ever read was called "Antifragile" by Nassim Nicholas Taleb.
I am sorry, but for me that book was a no. It just felt like a self help book, but for programmers, which is kind of ok if you are feeling any sort of personal trouble in the field. Not that this is not already told on the back cover, but no, I would not call this book the best development book. I did not buy it, instead, it was the result of participating in a local dev Google something, but it really surprised me h…
Did you at least read it?
I am sorry, but for me that book was a no. It just felt like a self help book, but for programmers, which is kind of ok if you are feeling any sort of personal trouble in the field. Not that this is not already told on the back cover, but no, I would not call this book the best development book. I did not buy it, instead, it was the result of participating in a local dev Google something, but it really surprised me h…
Have you (or anyone else) read Code Complete? If so, how do you feel about it? I started reading it because everyone recommended it, but I stopped at page 100 or so, because I felt it was getting no where.
The book is about the tiny details of coding. Getting the small things right, as in any sport or profession, gives you the tools to get the big things right.
But if you are in a section that bores you, skip around a bit!