Hacker News new | past | comments | ask | show | jobs | submit login

Three boks I'll recommend you read as soon as possible.

1) The Mythical Man month

3) The Pragmatic Programmer

3) Code Complete.

The thing about these books, well atleast 1 and 3 is that when they were written they broke new ground. Or if that phrase bother you, they were the first mainstream publications that brought their core ideas to developers.

Reading these books early in your career will help cement these best practices.

Reading these books after you've been a practicing programmer means,IMHO, that the return you get from reading them goes way way down.

You'll find that you've already learned all/most? of what they are trying to teach.

You'll find yourself getting frustrated that they are preaching what you already know as common sense and first principles.

Or put another way, I'm not sure there is much that someone who has programmed for 5-10 years can get out of those books that they haven't picked up somewhere else already or learned the hard way.

A quick reference for the important points in Pragmatic Programmer :https://blog.codinghorror.com/a-pragmatic-quick-reference/

Code Complete: http://codecourse.sourceforge.net/materials/Code-Complete-A-...

Thank you. The most value I get from these kinds of books is to become aware of important concepts so that I can actively work on improving them. In other words: what I seek from these books is the mental framework that experienced developers rely on, the rest is mostly noise.

I read through Code Complete 2 cover to cover my first year and I agree with parent it's more useful early on than later. There's a lot of discussion around best practices; I think there's an entire chapter on strategic whitespace. All the stuff in there makes sense, but it cements why it's important.

Definitely check out "The Pragmatic Programmer"! There's definitely some good nuggets in there that helped me. Distinguishing full-blown prototypes vs. prototypical kernels that can be productionized, a.k.a. tracer bullet prototyping, is one.

This x1000. I'm only just getting to reading these now 10 years into my career and I find them to be a bit useless for me since I've already picked up bits and pieces of each throughout my past jobs/companies. Would have been much better off earlier on if I had just read these beforehand.

I always started and stopped reading Code complete book. The most recent strategy that really worked for me was. I googled summary notes for that book to recognize the topics that I wanted to learn and ditched the ones that are redundant.

This rejuvinated my interest and productivity for reading that book.

I kinda wonder, after all these years, if there would ever be a new edition of the Pragmatic Programmer; or even a discussion from the authors on how their thinking has evolved over time.

Applications are open for YC Summer 2019

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact