It is by you. It's the software engineers guide book. Um and of course I'm I'm playing to the crowd, but it it is genuinely genu genuinely um a very very sharp book.
On The Pragmatic Engineer podcast (2025-10-29), asked for a book he recommends; the book is by the host, Gergely Orosz, as he says. Quoted from the video's YouTube captions.
Minimize distractions and shallow work. Carve out long stretches for intense focus and complexity. Build rituals and routines to regularly do deep work. Protect this time.
A post distilling his favorite takeaways from about 40 soft-skills books for developers and eng leaders.
Break down big goals into small, manageable habits. Focus on processes, not outcomes. Create obvious cues and routines for habits to make them easy to start.
Empower and challenge team members instead of micromanaging. Get people thinking and taking initiative. Create space for people to contribute beyond their official roles. Draw out their skills.
Understand the two systems driving decisions - fast intuitive vs. slow analytical thinking. Know their biases. For complex analysis, create space from intuitions and emotions. Slow down and use structured reasoning.
Directly challenge people when their work needs improvement - be caring personally but candid professionally. Praise good work clearly and sincerely. Show you notice and appreciate their efforts.
Disruptive innovations often come from outsiders and new entrants, not incumbent leaders. Focus on customers’ evolving jobs-to-be-done, not existing product categories. Be ready to cannibalize your own products.
Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.
The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.
A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.
The shading behind a date shows how dated a recommendation is for its kind of thing.
The shading behind a date shows how dated a recommendation is, for its kind of thing. Fully green is recent. It drains a quarter at a time as the post gets older, and is empty once it reads as dated.
What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The shading is gone after about:
Hardware, services4 years
Software5 years
Podcasts, courses, other8 years
Books25 years
Stripes mean the post carries no date and the date shown is an estimate. No date at all, no shading.