How AI is reshaping software engineering beyond the editor — delivery, leadership, business outcomes, and the people behind the work.

Software Engineering in the AI Era

Small practices for better engineering teams.

The Engineering Team Operating Layer

What happens when AI compresses delivery cycles but humans still need time to think, feel, and align.

Human Latency in AI-Accelerated Teams

Turning philosophical ideas into practical tools for building software — prioritization, design, delivery, and culture.

Philosophy for Builders

Exploring the emotional side of building software — burnout, identity, ambition, loneliness, and healing inside modern tech culture.

The Quiet Side of Tech

Operating rhythms, artifacts, and guardrails that make triads click — fewer hand-offs, clearer decisions, happier teams.

Cross-Functional Glue: EM x Product x Design

Practical reflections on building trust, coaching people, and leading remote teams at a sustainable pace.

Empathetic Remote Management

A series exploring how AI is changing the way we build software and everything around it: how teams work and deliver, how we measure whether things are actually improving, how leaders navigate new decisions, and what these changes mean for businesses, careers, and the people experiencing them. Drawing on practical experience, engineering leadership, and recent research, each article explores a different part of this transition, including the questions we still don't have clear answers to.

AI makes engineers feel faster. Knowing whether the team delivers better means measuring the whole path, the human review it consumes, and what it costs.

Faster Engineers Are Not Yet Proof of a Faster Team

A series about the small practices that help engineering teams turn ambiguity into decisions, decisions into delivery, and delivery into learning. Not ceremonies for the sake of process, but lightweight operating habits grounded in product discovery, engineering strategy, team cognition, risk management, and continuous improvement.

A One-Page Bet Map helps engineering teams clarify outcomes, constraints, bets, and non-goals before roadmap tickets take shape.

The Small Map Before the Roadmap

A lightweight Decision Note helps teams keep the memory of why a choice was reasonable, without turning every trade-off into heavy documentation.

Decision Notes Over Decision Theatre

Risk Sketch is a 20-minute practice for surfacing product, design, and engineering risk before late surprise becomes tense rework and ugly scope cuts.

Risk Sketch: Surface Risk Before It Becomes Rework

Approach Review helps engineering teams surface trade-offs before pull request review turns into late design debate, tense threads, and costly rework.

Approach Review Before the Pull Request Gets Expensive

A Shipping Debrief helps engineering teams turn meaningful deliveries into one concrete, testable improvement to how they plan, build, review, and learn.

Shipping Debrief: The Work Is Not Done When It Ships

A series exploring the growing gap between machine speed and human processing in engineering teams. AI shrinks cycle times, but trust, clarity, and emotional integration don't compress at the same rate. Each post examines where that gap shows up — in decisions, in team dynamics, in the quiet weight people carry between sprints — and offers practical ways to close it without slowing down.

AI compresses delivery cycles, but trust and emotional processing don't. That gap — Human Latency — is the friction your team can't ship away.

AI Shrinks Cycle Time. Humans Don't.

AI-driven productivity follows a predictable curve — boost, stretch, crash. Three operational limits help teams sustain intensity without burning through attention and judgment.

The AI Fatigue Curve: Why Intensity Is Not Free

Technical debt grows when you rush code. Emotional debt grows when you rush people. In AI-accelerated teams, both compound faster than ever.

Emotional Debt: The Technical Debt AI Accelerates

Shipping isn't the finish line. The 15 minutes after a release — naming what was learned, felt, and carried — are what keep a team coherent under speed.

Aftermath Over Delivery: What Teams Skip After Shipping

Forced alignment creates compliance, not direction. Three leadership patterns — containment, clarity, repair — help teams stay coherent without flattening disagreement.

Leading Without Forcing Alignment in AI-Accelerated Teams

A series that applies philosophy as an engineering lens: not as abstract theory, but as a way to make clearer trade-offs, build more sustainable systems, and lead with more intention. Each post starts with a concept (Stoicism, memento mori, Socratic method...) and translates it into concrete frameworks, questions, and habits you can actually use while shipping.

Memento mori isn’t morbid — it’s clarifying. A practical lens to prioritize what we build, protect our attention, and choose work we can actually sustain.

Every Yes Kills Something

A stoic lens for shipping in unstable environments: reduce delivery anxiety by separating what you can control from what you can’t — and designing plans around inputs, not predictions.

Control the Inputs, Not the Outcomes

A Socratic checklist for requirements: uncover assumptions, prevent scope drift, and pull discovery forward—before you build.

The Unexamined Backlog

Pascal warned that we flee stillness by staying busy. In engineering, the flight often looks like optimizing — and it's worth learning to notice.

When Systems Become Self-Soothing

Nietzsche's amor fati means loving what happens. In engineering, that translates to postmortems without shame — and systems that learn from every incident.

Series Library

Software Engineering in the AI Era

The Engineering Team Operating Layer

Human Latency in AI-Accelerated Teams

Philosophy for Builders