Show HN: 14 Habits of Highly Productive Developers – New Book
14habits.com
14habits.com
I never thought I'd say this, but - yes - I just published a book!
14 Habits of Highly Productive Developers is now available for everyone.
It's everything I know about productivity, tech career, and side projects into one package. I spent 3 months writing this, 1 month working on the launch, and 10+ years living these ideas.
To be honest, I never wanted to write a book, but I believe that being a developer is more than knowing the hottest tools.
You can learn the most popular frameworks, use the best programming languages, and work at the biggest tech companies, but if you cultivate bad habits, it will be hard for you to become a top developer.
Because of that, I decided to reach out to the best developers I know and ask them tips on how to be more productive.
I went after tech giants such as Google, Amazon, and Microsoft. Powerful startups such as Spotify, GoDaddy, and Shopify. All the way to established organizations such as Citibank and The New York Times.
This book is a collection of valuable learnings not only from me but from experienced programmers from all over the world.
I hope you like it :)
Let me know if you have any questions! I'm here to answer every single one of them.
I don't know what the opposite of Cognitive Dissonance is called, but now I know what it feels like.
E.g. "I spoke in [more than a hundred conferences]" - I think "I spoke at" is better. However, my background is UK English so perhaps this is an Americanism.
Next para:
"I was fortunate enough to be in contact with some of the best software engineers in the industry, but I also met a lot of programmers who are still doing the same thing for many years."
"I was fortunate enough to come into contact with some of the best software engineers in the industry, but I also met a lot of programmers who just spent many years repeating the same thing."
The graphics are quite rough and too large - the actual amount of text per page on the PDF is very low. This compounds the feeling of the text itself feeling very surface level.
> Instead, we should practice JOMO (the joy of missing out), which is mostly about being happy and content with what you already know.
Here you introduce a new concept and never mention it again. Instead of paving a road to drive on in the next few paragraphs, you immediately introduce a plethora of heavyweight ideas including the practice of saying no and of noise discrimination.
All of these points are good ones, but because they're passed over so quickly with no explanation it's going to be hard for someone who isn't familar with them to unpack them and extract learnings.
Minor nitpick: I feel like the links on all those company icons is unnecessary (alt text on hover would be fine).
Interestingly taking the first letter of each company leads to the acronym - GAGMASS.. A bit catchier than FANG :)
I agree the links on all those company icons is unnecessary. I just put it over there in case people didn't know the logo.
About the TOC, I believe you might have missed that. It's on the "What's inside?" section of the site.
GAGMASS - that's funny :P
FWIW there's 9 upvotes on my earlier post so maybe that means 8 other people had the same issue as me, not sure.
I don't want to comment much on the book because of ^ but there is something that I found a little bit off putting for me.
It is the obsession with American big tech (the biggest tech companies and well known startups). The book suggests that all such companies have it figured out, that all engineers working there are the most productive and best in the industry. I personally don't believe it and I am not sure why a productivity book should be so heavily based around it.
As an example take this question from the book "What's so special about individuals who create the most used applications in the world?" I really really just want to answer "Nothing".
Anyways there goes my little rant... Definitely congrats on publishing a book, it is a struggle!
When I was starting my career, I always looked at those companies as dream jobs. The amazing offices, the culture, everything was eye-catching.
As I started to get older and more experienced, I noticed that those companies are not that special. They have issues, problems, and conflicts like any other company. Don't get me wrong, those companies are still amazing and their impact is undeniable.
I see this like sports. There are amazing teams out there, but the ones with more capital are able to go after the best players in the market. This doesn't mean that small teams don't have talented players.
The only reason why I invited those individuals is because they are the most talented programmers I know. I'm pretty sure there are amazing people working on smaller companies, but when I looked at my past co-workers and developers from my circle of friends, those were the ones I wanted to hear more from.
Anyways, hopefully this will show a little bit more about my decision making process.
Good luck on your book! I'm excited to take a look, is there any pre-sale already?
I am not selling the book yet, I have just a sign up page for now (https://efficientdeveloper.com). My take will be more about software development as a whole rather than just the productivity part, with productivity being just an angle of what I will cover in the book.
as a fellow book author tho... you bet I went after big names for my testimonials.
https://www.amazon.com/Programmers-work-Interviews-Susan-Lam...
I read the sample chapter and enjoyed it so much, I bought the book on gumroad. But ONE BIG NIT: the sample chapter is pdf, but the book is not. Can you please provide me a pdf of the full book? Email on my profile.
Looking forward to reading the rest and providing feedback.
I hope you sell a bunch of books and write some more :-)
Thanks you so much!
Why did you quote Zig Zigler? Seems a little out of place. Also, I felt that the first chapter needs to be more compelling - but maybe that's just me.
On every chapter, there's a quote. This particular one has a Zig Zigler quote because it matches pretty well with the content of the chapter.