Book · 2015
The Effective Engineer
by Edmond Lau
A former Quora engineer's framework for shipping work that matters, built around one question: what actually moves the needle?
What does Reddit think of The Effective Engineer?
Thirty-five mentions across seven subreddits over seven years, and the book still can't escape being paired with The Pragmatic Programmer. r/cscareerquestions owns 18 of those mentions and treats the title mostly as vocabulary — "effective engineer" as a standard the commenter is holding someone else to, not as a book they're discussing. The sentiment there is flat. r/ExperiencedDevs is where the actual signal lives: 7 mentions, the warmest sentiment in the dataset, and a ↑183 comment that pairs it with The Pragmatic Programmer as easy reads with real takeaways. The r/programming appearance (↑142) went sideways fast — a quote about engineering efficiency prompted pushback on the "just build stuff" mentality, which is about as close to literary criticism as that sub gets. r/devops and r/learnprogramming each checked in at 3 mentions, both neutral. r/Python and r/webdev each contributed 1. The through-line in the positive reads: understanding business value makes the technical advice land. The through-line in the critical reads: the title gets used as a punchline more often than the book gets read.
Community feedback & reader fit
Themes
- · High-leverage activities and prioritisation
- · Engineering productivity over raw output
- · Business context as a force multiplier
- · Mentorship and career growth
- · Avoiding low-value work and meeting overhead
Common praise
- + r/ExperiencedDevs recommends it alongside The Pragmatic Programmer as one of the few career books that actually earns the shelf space.
- + The framing around business understanding clicks for engineers who've already hit the ceiling of pure technical improvement.
- + Short enough that the ideas stay with you after a single weekend read.
Common criticism
- − r/cscareerquestions uses "effective engineer" as a slur more often than a compliment, which tells you something about how the title landed in the wild.
- − The r/programming thread suggests the efficiency framework slides into "just build stuff" territory that experienced engineers find naive.
Who it's for
If you're two or three years in and feel like you're shipping tickets without moving anything important, this is the book that names that problem. r/ExperiencedDevs readers respond to it; r/cscareerquestions ones tend to quote the title back at people rather than read it. Pass on it if you want system design depth — nothing here competes with Designing Data-Intensive Applications on that front. Best read alongside The Pragmatic Programmer, which is how the ↑183 comment from r/ExperiencedDevs frames it.
Mentions over time
Which Reddit comments matter for The Effective Engineer?
Top-upvoted quotes across the subreddits where this book is mentioned. Click through to read the full thread.
“One of the SUPER common interview questions at LOTS of companies is "what happens when you type a URL in a browser and hit enter", and it doesn't take long to realize a HUGE chunk of that is networking. That should tell you something meaningful, like, modern software engineering is almost entirely …
“1. The Effective Engineer: How to Leverage Your Efforts In Software Engineering to Make a Disproportionate and Meaningful Impact 2. The Pragmatic Programmer: Your Journey To Mastery They're easy to read and might have some takeaways for you.
“> Improve the efficiency of their engineering teams so that they focus as much time as possible on building, solving problems, and improving features. While I understand the desire not to overload engineers with meetings and bureaucracy, I think the "we should only build stuff" mentality that is co…
“Honestly. It's crazy to think that some of these "engineers" are even engineers. If they are too dense to see through this obvious grift? Then maybe they're too dense to be an effective engineer lol
“The OPs who post these sorts of posts hardly ever post an (anonymised) version of their resume, so I wonder how they do with following up on feedback generally in their job seeking technique...it would help them to succeed. Isn't being diligent a part of the skillset you need to be an effective e…
“Hey! Im planning on doing content on this exact topic, so I know exactly how I would go about it personally: 1) Go to meetups for Software. Since college is not an option for you, there are tons of apps out there like LinkedIn or Meetup that will let you go to free workshops, zoom classes and meet …
“A series of good mentors. I've been lucky to cultivate a few during my career but my first two were the most critical. A professor in grad school "recognized my desire to learn more than just what was needed to get the grade" (his words not mine). He exposed me to a lot of knowledge that I wouldn'…
“I feel like everyone places a big emphasis on tech domain knowledge, but I’ve found that understanding the business goes much further both in making you a productive and effective engineer. No matter what your industry, understanding why a case or feature has value makes you better able to deliver…
Convinced? Pick up The Effective Engineer
What else does r/cscareerquestions read?
Other books mentioned in the same sub, ranked. Shared-sub overlap with this title breaks ties.
Cracking the Coding Interview
Gayle Laakmann McDowell
The book that turned software hiring into a sport — written by the ex-Googler who introduced programming challenges to the process in the first place.
Designing Data-Intensive Applications
Martin Kleppmann
A backend engineer's field guide to the tradeoffs behind every database, queue, and distributed system you will ever touch.
The Pragmatic Programmer
Andy Hunt
Two veterans hand you a checklist for the craft: don't write code you don't need, own your tools, and fix the broken window before someone else does.
Clean Code
Robert C. Martin
The book 536 Reddit threads cite when arguing about naming variables — revered by beginners, argued over by seniors.
Design Patterns
Erich Gamma
The 1994 Gang of Four catalog that named 23 object-oriented patterns, gave developers a shared vocabulary, and taught a generation to over-apply both.
The Mythical Man-Month
Frederick P. Brooks Jr.
Fred Brooks spent the 1960s building IBM's OS/360 and wrote down everything that went wrong — in 1975, and it still lands.
The Effective Engineer — frequently asked
What does Reddit actually think of The Effective Engineer?+
Mixed, depending on the sub. r/ExperiencedDevs is broadly positive — a ↑183 comment pairs it with The Pragmatic Programmer as worth reading. r/cscareerquestions, which accounts for 18 of the 35 total mentions, mostly uses the phrase as a benchmark for other people's failings rather than discussing the book itself.
Is The Effective Engineer worth reading if I already own The Pragmatic Programmer?+
Probably yes. The r/ExperiencedDevs comment with ↑183 upvotes recommends both together and treats them as complementary rather than redundant. The Pragmatic Programmer is craft-focused; The Effective Engineer is more about where to aim the craft. They don't overlap much.
Is The Effective Engineer relevant for senior engineers or is it entry-level advice?+
Depends on where you are. The ↑43 r/ExperiencedDevs comment makes the most pointed case for the book's core argument — that understanding business value is what separates productive engineers from fast ones. That framing resonates more at mid-to-senior level. The r/cscareerquestions crowd skews earlier career and mostly uses the title as a shorthand.
Does The Effective Engineer hold up in 2026 or is the advice dated?+
The data doesn't suggest decay — 6 mentions in both 2024 and 2025 is consistent with its historical pace. The r/devops and r/learnprogramming appearances as recently as January and February 2025 suggest it's still in circulation. The core argument about leverage and high-value work is structural enough that it doesn't expire with a particular tech stack.