|
K&R from decades gone by.
“If only you could see what I’ve seen with your eyes”
|
|
|
|
|
That was a great book. Short and concise. You could get up and running in C in no time.
|
|
|
|
|
I was thinking about that just the other day. "Code" by Charles Petzold.
|
|
|
|
|
PIEBALDconsult wrote: "Code" by Charles Petzold.
It's an amazing book that helps tie software and hardware all together.
I've learned stuff in that book that you cannot learn anywhere else. I guess maybe in high-level university courses maybe.
|
|
|
|
|
You might enjoy the Nand to Tetris courses and the book that goes with them: nand2tetris[^]
The cover some of the same territory as Code but along the way you actually created a simulated computer and by the end of the whole thing, you're able to run Tetris on it.
|
|
|
|
|
That one's in the running for me.
Real programmers use butterflies
|
|
|
|
|
|
I found Code to be amazing for the first half of the book, but it lost clarity for me in the second half.
It just seemed that he lost the desire to make his more advanced information approachable.
"Qulatiy is Job #1"
|
|
|
|
|
I have a COBOL book I like alot. It raises my monitor just right.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
|
|
|
|
|
MarkTJohnson wrote: I have a COBOL book I like alot.
As I read that sentence I was thinking..."Ewww..., really?"
MarkTJohnson wrote: It raises my monitor just right.
NOw that makes sense!!
|
|
|
|
|
MarkTJohnson wrote: It raises my monitor just right.
Petzold's Programming Windows Fifth Edition does it for me!
|
|
|
|
|
I use Inside Ole 2
Real programmers use butterflies
|
|
|
|
|
C# In Depth 3rd Edition (Jon Skeet)
Publisher is Manning
There is a 4th edition: Amazon[^]
|
|
|
|
|
Slacker007 wrote: C# In Depth 3rd Edition (Jon Skeet)
If I owned a business and needed a programmer I would hire you immediately.
That's a very tough book.
I've read the first 3 chapters of that book 2 or 3 times but couldn't get through more.
I'm a bear of little brain. Just couldn't get there. Maybe I'll try again this year and see if I can get through chapter 4 this time.
|
|
|
|
|
Zen and The Art of Motor Cycle Maintenance (Robert M. Pirsig)[^]
And it's about as much about programming as it is about Zen Buddhism or motorcycle maintenance. But ... learn the right lessons from it, and you can cope with development (and make a start of fixing motorcycles as well).
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Good choice!
Real programmers use butterflies
|
|
|
|
|
It's one of the few highly acclaimed books I was not able to finish. Couldn't go beyond 20 odd pages.
Another is Catch 22.
Cheers,
विक्रम
"We have already been through this, I am not going to repeat myself." - fat_boy, in a global warming thread
|
|
|
|
|
I'd have to say the GoF patterns book.
|
|
|
|
|
I have read the introductory chapters (intro and chapter 1) and then skipped around a bit. Mostly too hard for me. I like that they say, "Prefer composition over inheritance."
That's what that entire book is about for me. I remember back when OOP was growing in popularity (1991 or so) and it was all about inheritance. Then GoF explains, "no it's about composition". That's good stuff!
|
|
|
|
|
It's good as a reference. Just read the general description of each pattern and look at the details when you think you need a pattern but the UML diagram doesn't give you a good enough idea of how to write the code.
As much as anything, the fact that it gives a name to each pattern saves lots of time during design discussions, because everyone can quickly understand an approach being suggested. It's about much more than composition, though.
|
|
|
|
|
Greg Utas wrote: gives a name to each pattern
Which is the only real value of the book. I bought a copy simply so I could be sure I knew what people were talking about and know which people had no idea what they were talking about.
|
|
|
|
|
PIEBALDconsult wrote: Which is the only real value of the book.
I've gotten some mileage out of the visitor pattern but I didn't learn it from that book. In fairness though, they describe it for people that didn't already learn it, and it's one of the more useful patterns to know, IMO.
Real programmers use butterflies
|
|
|
|
|
That's interesting, because I don't recall using Visitor. It probably depends on your problem domains. The patterns that resonated most with me were Chain of Responsibility, Abstract Factory, and Observer, and the simpler Singleton and Flyweight. I'd already used them but now had good names for them.
|
|
|
|
|
Yeah it really depends on what you're doing. I've just had several occasions where I basically need to query an object model, and a visitor can be a foundation of that.
Real programmers use butterflies
|
|
|
|
|
For me, it's a toss up between Kernighan & Ritchie's The C Programming Language, and Aho, Kernighan and Weinberger's The AWK Programming Language. Other books I remember from college days include Fortran IV With Watfor and Watfiv, and a two book set of Shelley & Cashman on Cobol. Those are all still around, somewhere in the attic, along with a lot of seriously outdated hardware. I know there's a 300 baud modem with the acoustic couplers for a standard Bell desk phone's handset up there, and a couple of cases of 80-column cards.
|
|
|
|