Ask HN: Which books have helped you the most professionally?

For a non-cs book, checkout Deep Work by Cal Newport. It's been a little while since I read, but what struck me most is the mindset to avoid distractions.

You've Only Got Three Seconds by Camille Lavington. Basically helped me to understand what I can do to make a good impression on others.

How to win friends and influence people

If you want to embrace DevOp culture, where it comes from, why is it important and the reality of medium big businnesses, then you definitely want to read the Phoenix project

Mythical Man Month

Difficult Conversations

Primal Leadership

Necessary Endings

The War of Art - about overcoming that nagging resistance to getting stuff done that we all feel.

early in my career, those two books were on my desk continuously: https://www.amazon.com/Network-Programming-Perl-Lincoln-Stei... https://www.amazon.com/Mastering-Algorithms-Perl-Practical-P...

later, it was time for https://www.amazon.com/How-Win-Friends-Influence-People/dp/0...

The Power of Habit by Charles Duhigg

Would it be ridiculous if you upvoted this comment??

Never Split The Difference - Chris Voss

This book has made a much greater negotiator both professionally and personally.

“Would it be ridiculous if” and “How am I supposed to do that?” Have saved me 100s of thousands of dollars!! The only negative point is that the negotiation style does not work on my wife ever since she read the book.

Software Craftsmanship from mancuso helped me a lot to find meaning in my work as a software devloper

Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems by Martin Kleppmann. Absolute best book on system design.

How to win friends and influence people. Helped me solve some approaches to handling people in general and highlighted a few approaches that I had been taking that were actively causing me problems.

The Secrets of Consulting: A Guide to Giving and Getting Advice Successfully by Gerald Weiberg. [1] Helped me understand why technical problems are rarely just technical.

Working effectively with legacy code by Michael Feathers [2]. Practicing some of the techniques in this helped me get my foot in the door in a job long ago where one of the interview scenarios was "This is broken, go ahead and fix it.". I recommend reading this for anyone working on a code base that's been around for a while.

--

[1]: https://www.amazon.com/Secrets-Consulting-Giving-Getting-Suc...

[2]: https://www.amazon.com/Working-Effectively-Legacy-Robert-Mar...

"What Got You Here Won't Get You There: How Successful People Become Even More Successful" by Marshall Goldsmith helped me become a better teammate and communicator.

SICP, the foundation on which my career rests.

"How to Solve it" was great for me from an abstract problem solving point of view. It helped me get better at seeing which abstractions help solve an otherwise difficult problem, which is a useful skill to have for coding interviews and, really, most technically difficult problems encountered during the work day.

33 Strategies of War. It's good for dealing with any and all types of conflict, including conflicts with yourself. Half of the book is unconventional techniques most people don't even think of.

Similarly themed is Extreme Ownership, which covers leadership in chaotic situstions.

Militaries are designed to deal with the chaos of war, and a lot of principles apply to the chaos of software engineering too.

One I haven’t seen mentioned yet is Time Management For Systems Administrators. The concepts also work for devs too.

ReWork by Jason Fried and David Heinemeier Hansson (good reference on good principles)

Traction by Gino Wickman (how to create SOPs & scale)

Authority by Nathan Barry (how to develop an audience)

As a small business owner I'd have to say E-Myth Revisited and Work the system.

Because once you learn systems thinking, you see the world totally differently and from a business point of view, understanding how their systems work is like getting to have a look at the source code of that business.

"Large-Scale C++ Software Design" by John Lakos. The only book (as far as I know) that really teach you the nitty gritty of handling very large scale systems (not just C++ systems). Something I have needed more than once in my career.

Pitch Anything - About selling and the psychology of selling. Really need to re-read that one actually.

And +1 for Deep Work, So Good They Can't Ignore You or The World Beyond Your Head. They made me realize that being in a profession where you can reach "flow state" actually is a privilege.

I'm no professional but I was very impressed by the immediate utility and domain independence of what I gained from reading "Thinking, Fast and Slow".

I've always felt that intelligence is largely cultivated (or at least a significant portion of what we commonly refer to as 'intelligence'), and much of this book seemed to agree and offered constructive advice on improving ones cognition, along with making use of many quirks, oddities and primitive habits our brains have been endowed with.

First 90 days from HBR

POODR - Practical Object oriented design in ruby. Changed my way of coding entirely, brought me to a completely different level and pushed an even bigger growth