In my X posts on 2026‑10‑23 I reflected on personal branding and how to communicate impact effectively, emphasizing that we’re all continuously "selling" ourselves both personally and professionally.
The Kindle launch of The Multiplier Mindset quickly became #1 New Release and #1 Bestseller on Amazon across three categories within a day or two.
The physical print edition is scheduled for release on October 31 2026.
I decided to replace the habit of saying “my work speaks for itself” with proactive impact statements to avoid under‑communication.
For concrete guidance I point readers to the linked article (https://t.co/NZ8qClUovA) that outlines a framework for structuring impact communication.
I see "being hands‑on" as a requirement in almost any engineering role these days. From middle managers to VPs and even CTOs.
Most engineering professionals think that writing (generating) code is the best use case for AI. But some of the biggest opportunities are actually outside of coding.
2 years ago, the engineering team's structure was fairly standardized, 2‑pizza cross‑functional teams and an engineering manager leading the team.
These observations reinforce my earlier decisions to stay hands‑on across seniority levels and to apply AI to non‑coding communication tasks.
I decided to stay on Substack after being asked to migrate the newsletter; I felt it was the right choice for my strategy.
Every hour you save on repetitive work is an hour you can invest in higher‑leverage activities, like mentoring your team or solving problems.
Try to automate anything that doesn’t require human judgment.
Always keep in mind that AI is like any other tool, it’s just more powerful.
It can help you generate ideas, code, or give feedback, but you’re still responsible for deciding what’s correct and what really matters.
In late October 2026 I announced the Kindle launch of The Multiplier Mindset and celebrated a rapid surge to #1 New Release and #1 Bestseller on Amazon across three categories, while also committing to a no‑local‑development workflow and emphasizing clear specifications before letting AI generate code.
The book became #1 New Release and #1 Bestseller on Amazon across 3 categories within a few days of the Kindle release (tweeted 2026‑10‑19 13:42 UTC).
The physical print edition is scheduled for release on October 31st, 2026.
Decision: No more local development – I will avoid pushing AI‑generated code directly to main after discussing with @KevinNaughtonJr.
Decision: Emphasis on definition before coding – the better the specification, the less time spent fixing AI mistakes.
Gratitude: “I’ve spent almost a year writing this book, and seeing this kind of response makes all those hours totally worth it.”
Caveat: Faster code generation doesn’t necessarily mean better software.
Many companies use a higher‑tier LLM to write the spec and a lower‑tier LLM to build the product.
Number 1 principle of spec‑driven development: Write the smallest spec that unambiguously specifies the system.
If a section feels like fluff, cut it.
If a decision feels obvious, write it down anyway.
Obvious to you is not the same as obvious to the model.
I decided to adopt a two‑tier LLM workflow because higher‑tier models produce clearer, more comprehensive specifications while lower‑tier models are cheaper and faster for implementation, reducing overall cost without sacrificing quality. I also committed to enforcing minimal, unambiguous specs to minimise interpretation variance, and to explicitly record even “obvious” decisions so the model doesn’t make incorrect implicit assumptions.
My Kindle release of "The Multiplier Mindset" hit #1 New Release in Computer Engineering on Amazon on the day of release (2026‑10‑16).
I positioned the book as a senior‑engineer handbook because the market need is for leaders to "make the people around you better" now that AI agents can write most code.
I dedicated a full chapter to using AI as a successful multiplier, providing concrete prompts and workflow guidance.
- Practical 4‑step AI‑assistance workflow:
I recommend prompting LLMs to challenge assumptions, provide alternatives, and surface missed aspects as a thinking‑partner technique.
Peter Bell, Founder/CTO of Gather.dev, endorsed the book as a hand‑off for CTOs asking senior engineers what their role now is.
I will speak on October 23 in London at React Advanced about building AI‑native engineering teams.
- Share a tech spec or architecture decision record with an LLM; ask it to stress‑test the idea.
- Draft a script for a difficult conversation, get LLM feedback, then rehearse.
- Share a specific problem clearly; ask the LLM for solution ideas and refine your understanding.
- Ask AI to review your writing, applying changes manually to preserve your voice.
I posted a series of short X messages on 2026‑10‑15 that introduced my “multiplier” mindset, argued that engineers should amplify the effectiveness of everyone around them, and positioned LLMs as the newest, more powerful engineering tool. I also announced the pre‑order for my e‑book and thanked @johncrickett for his support.
Being a multiplier means being someone who amplifies the productivity and effectiveness of the everyone around them, not just focusing on their own output, but elevating the entire team and the organization.
And an engineer, who is a multiplier doesn’t just ask, “What can I build?”, they ask, “How can I make everyone around me more effective?”.
The goal of engineering has never been to do everything yourself, we've always used tools to free up our time for higher‑leverage work.
So using LLMs is the same thing, just they are more powerful and the outcomes are much less predictable.
E‑book and pre‑order now available!
More info here: https://t.co/Fr38w359Bk
@johncrickett Thanks John!
I reflected on the AI‑centric engineering landscape in mid‑October 2026, noting that token budgets quickly become a bottleneck, that engineers now lean on AI for rapid code‑base onboarding, and that Anthropic’s new version‑control system dramatically outpaces git at AI scale.
- “The problematic part is that tokens will run out quick when you try to build this 😂”
I observed that “The problematic part is that tokens will run out quick when you try to build this 😂”.
I noted that “Great engineers these days don’t spend hours trying to understand a codebase by going through it file by file or reading every word of the documentation.”
I classified engineers into three camps: Refusers, Overreliers, and Multipliers, as described in “When it comes to using AI, most engineers and engineering leaders fall into 3 camps:”
Anthropic’s AI‑centric VCS merged ~2,500 code changes per day in May 2024, then >30,000 per day in September 2024, and completed a full monorepo migration from git in five months.
- “Great engineers these days don’t spend hours trying to understand a codebase by going through it file by file or reading every word of the documentation.”
- “When it comes to using AI, most engineers and engineering leaders fall into 3 camps:” – Refusers, Overreliers, Multipliers.
- Anthropic merged ~2,500 code changes per day in May 2024, then >30,000 per day by September 2024, and fully migrated a monorepo from git within five months.
In mid‑October 2026 I posted a thread that introduced a short, tongue‑in‑cheek development style I call “vibe‑coding”. I defined a pragmatic engineer as someone who “finds the best possible solution possible within the constraints of the real world, not the ideal world.” The post listed a set of concrete constraints that shape those decisions and described several quick‑prototype projects (financial report, messaging app, PDF viewer, GitHub clone) that I built using vibe‑coding because time and stakeholder pressure outweighed waiting for polished solutions. I also noted that only open‑sourced replacements “count” in the community.
A pragmatic engineer finds the best possible solution possible within the constraints of the real world, not the ideal world.
- Budgets
I chose to “vibe‑code” quick prototypes for a financial report, a messaging app, and a PDF viewer because the immediate need (my wife wanted the report) outweighed waiting for a polished solution.
I plan to open‑source the GitHub clone so that the vibe‑coded replacement “counts” within the community.
- Legacy code
- Project schedules
- Regulatory frameworks
- Existing hardware and infrastructure
- Product requirements (which may change)
- Team members' knowledge and expertise
- Team members' and stakeholders' personalities, relationships, and motivations
On 2026‑10‑12 I shared a short thread on X that highlighted three complementary observations about engineering burnout, bureaucracy, and the multiplier mindset. I argued that engineers burn out not from the act of building but from "fighting the system just to be allowed to build", and that large‑company bureaucracy and politics block real work. I also emphasized that elevating peers – making 5‑10 people around you 20 % better – creates far more impact than improving your own skills by the same amount.
Engineers don't get burnt out from building things. They get burnt out from fighting the system just to be allowed to build.
If you make 5-10 people around you 20% better, it's much bigger value than if you level up your skills by 20%.
In the discussion I clarified the two complementary cycles of software development: - Inner Loop – the speed of writing and shipping code. - Outer Loop – acquiring real user feedback, learning, and rapid iteration toward real outcomes. These definitions were described by Sulman Choudhry when contrasting average and elite teams.
I decided to emphasize improving the outer loop processes (feedback collection, testing infrastructure, signal analysis) rather than only increasing code throughput.
I decided to cultivate a strong engineering culture as the foundation for both loops, because there’s something a LOT more important than AI tools, and that’s a great culture.
I shared a series of X posts in early October 2026 announcing that my O'Reilly book The Multiplier Mindset entered production on 2026‑10‑10, that the print edition will be ready in the next 3‑4 weeks, and that I have written more than 250 articles over four years while attracting over 350 technical reviewer applicants. I also re‑emphasised my core engineering principle – the best engineers build the right things – and adopted simplicity as the primary decision‑making lens for AI‑augmented development.
The best engineers don’t just build things right. They build the right things.
What’s the simplest solution we could deliver?
I’ve written more than 250 articles over the course of 4 years on the Engineering Leadership newsletter.
More than 350 people applied to be technical reviewers for my upcoming book.
The book "The Multiplier Mindset" was moved to production by O’Reilly on 2026‑10‑10.
The print version of the book will be ready within the next 3‑4 weeks (by mid‑November 2026).
I began writing the manuscript in December 2025.
I chose to write a book rather than continue only with articles because I wanted to synthesize four years of insights into a lasting framework, despite the longer feedback loop.
I adopted simplicity as the primary decision‑making lens because AI can generate large codebases quickly, making unnecessary complexity a risk.
I ask myself, “How will this feature scale as the user base grows?”
I ask myself, “Could this implementation introduce security vulnerabilities?”
I ask myself, “What edge cases or unexpected inputs might cause this system to fail?”
- Refactor code that could be better – rename variables/functions for clarity and bring inconsistencies into alignment.
- Automate a repetitive task, such as starting the local environment or generating initial test data.
- Keep documentation updated whenever the code changes.
I decided that engineering leaders must dedicate regular time to credibility‑building activities (writing, speaking, LinkedIn upkeep) because it amplifies the impact of their technical work and serves as protective "armor" against reputational risk.
Engineering leaders should dedicate regular time to credibility‑building activities.
I adopt four team‑player traits to become a leader people want to work with: big‑picture focus, regular teammate check‑ins, learning and growing together, and improving my own teamwork skills.
I recognize my mistake of shielding the team too much and sugar‑coating problems, which prevented early collective problem‑solving.
My top three leadership tips are: build good relationships and communication practices; proactively discover problems others face and put effort into solving them; be transparent, give feedback, and ask for help when needed.
I note that Apple TestFlight’s review process is not conducive to fast CI/CD cycles.
I satirically outline a “12x MRR” pricing formula: triple the price, reduce usage by 50 %, add no extra value, and repeat the next year.
Enterprises value process navigation and consensus building.
Impact framework levels: Entry – personal productivity; Mid – team practice improvements; Senior – team‑wide operational transformation; Staff – multi‑team organizational improvements; Principal – company‑wide strategic capabilities.
Growth advice: shift focus from clever code to simple system design and human‑focused documentation to move from Senior to Staff.
These insights complement my earlier posts on fit, impact storytelling, and the “simple + documentation” mantra for staff‑level growth.
In early October 2026 I shared a series of X posts that highlighted my engineering philosophy for the AI era: the most valuable skill is deciding what to build and why, and keeping things simple. I also announced that my book The Multiplier Mindset was in production and that more than 350 people applied to be technical reviewers.
The best engineers don’t just build things right. They build the right things. In the AI era, where most of the code is generated, knowing what to build, why to build it, and keeping things simple is more valuable than ever.
“What’s the simplest solution we could deliver?”
More than 350 people applied to be technical reviewers.
I’ve written more than 250 articles over the course of 4 years on the Engineering Leadership newsletter.
The print version of the book will be ready in 3‑4 weeks from 2026‑10‑10.
Average engineers focus on: How to optimize syntax; How to write cleaner functions; How to adopt the newest framework.
Pragmatic engineers focus on: What actually needs to exist; Why it needs to exist now; What happens if we don't build it.
When the cost of generating code drops toward zero, the value of engineering judgment goes to infinity.
One of the worst feelings in software engineering is spending three months building a technically flawless feature and realizing nobody uses it.
Proud to announce my book "The Multiplier Mindset" published by O'Reilly!
In early October 2026 I introduced a three‑question checklist to anticipate scalability, security, and edge‑case issues, and I declared a “no‑permission‑required” policy so engineers can refactor, automate, or update docs whenever they see an improvement. I also marked the 4‑year anniversary of Engineering Leadership as a cultural milestone.
- How will this feature scale as the user base grows?
You don’t (usually) need permission to make things better.
- Could this implementation introduce security vulnerabilities?
- What edge cases or unexpected inputs might cause this system to fail?
Proactivity is defined as “taking initiative, anticipating challenges and driving solutions without receiving instructions or waiting for problems to arise.”
Most of engineering and business challenges are ambiguous, so you need to find out exactly what is needed and why specific problems exist.
I fully believe that proactive engineers are the best kind of engineers.
Engineers who create the biggest impact are not only technically capable of building great things, but are also trusted to make things happen, make good decisions, and also be a multiplier, to make others around them better.
Proactive engineers don’t wait for others to tell them what to do. They look at the big picture, see problems before they happen, take the initiative, communicate early and often, and look for ways to improve things.
I decided to emphasize proactive behavior in performance reviews and hiring rubrics because it directly links technical competence with broader impact, and to treat the multiplier effect as a measurable competency.
Success as an engineering leader = high‑quality work + making that work visible.
Credibility and social proof amplify the impact of visible work; "what you say" matters, but "who says it" is equally important.
I treat building credibility and social proof as "armor" that protects me from negative outcomes and gives me an advantage in tricky situations.
In early October 2026 I shared a series of X posts that distilled practical guidance for engineers who want to be effective team players and manage up, down, and sideways. Below are the four core team‑player traits I highlighted and three actionable tips for multi‑directional management.
- Take a step back from individual work and look at the big picture.
Effective engineering leaders must manage up, down, and sideways; neglecting any direction can damage the others.
A common mistake is shielding the team and sugar‑coating major issues instead of involving the team early.
- Top 3 tips for managing up, down, and sideways:
- Build good relationships and good communication practices.
- Proactively discover problems others face and put effort into resolving them.
- Be transparent, give feedback, and ask for help when needed.
- Regularly check in with your teammates.
- Learn and grow together as a team.
- Work on your own teamwork skills.
Small companies need someone who ships fast and figures things out alone.
The primary reason mid-level engineers struggle to reach Staff level isn't a lack of technical depth.
It's because they think technical leadership is about writing hyper‑complex, clever code.
Impact shows what changed for the better as a result of your work.
The 2026 version of "My code's compiling" meme :) Happy Friday and have a great weekend! https://t.co/DNFuPCcMYj
I decided to emphasize simplicity over cleverness for staff‑level growth because the barrier is over‑engineering, and I will tailor interview questions to surface candidates’ fit for fast‑ship or process‑heavy environments.
Engineers should craft impact stories with concrete numbers (e.g., "reduced deployment time by 30%") to demonstrate value at each seniority tier.