Conversations on shipping software that doesn’t fight you.

Is your engineering team worth its payroll?

With Scott Ritzheimer: why engineering teams feel expensive and slow – and how to fix the real bottlenecks. Ignoring investments and risk builds technical debt that drags everything down; short feedback loops keep a team on course better than long specs; and a small weekly investment in process improvement compounds into much higher velocity.

Why great engineering teams slow down

With Marilyn Jenkins: a roadmap looks fine on paper while the team grinds to a halt – usually overload, unclear priorities and no shared language between business and engineering. A four-step order of operations: shorten the path to production, build quality in, manage complexity as you scale, then earn predictability. Also why manual quality gates backfire, and technical debt as compounding investment.

/AI speed: faster code, slower business

With James Carman: AI shrank the engineering loop from weeks to days, so the constraint moved to the product loop – deciding what to build and whether anyone actually wants it. One client shipped so much in a single week the rest of the company could not absorb it. Also: tracking features, defects, investments and risks at the team level, and why a gamed metric beats an ignored one.

Why Most Software Teams Struggle to Ship (And How AI Changes That)

With Peter Parsons: software teams don't fail because they aren't smart – they fail because nobody ever taught them how to ship. Why teams reach for long-term planning before they have mastered short-term execution, how specialization quietly wrecks a team's ability to finish anything, and what AI actually changes about speed, safety, and rewriting an old codebase without blowing it up.

The Real-World Impacts of AI-Assisted Coding

With Thomas Erl: what AI-assisted coding actually does to a development team once the novelty wears off. Where the speed genuinely shows up, where it quietly relocates the bottleneck instead of removing it, and what it changes about review, ownership, and the skills a team needs to keep. The effects rippling through the industry rather than the demo-day version.

Prioritize, Ship, Repeat: Mastering Efficiency and Team Happiness

With Jess Dewell: your team isn't tired because it's working hard – it's tired because nothing finishes. Why efficiency means completing what matters rather than doing more, how constructive conflict builds the shared language a team runs on, why premature standardization blocks innovation, and how cutting context switching produces the thing people actually mean by team happiness.

From Code to Clarity: Building Better Software Faster

With Mike Mannino: why software projects struggle, and what leaders can actually do about the complexity they are swimming in. Delivery speed and product quality as outputs of the same system, the communication gap between business and engineering, and why a shared language across the two is the prerequisite for consistently shipping something customers value.

Beyond the Hype: What AI Can (and Can't) Do

AI as a productivity amplifier rather than a replacement. The strengths and limitations of current models, managing context in AI conversations, structuring effective prompts, and building agent-based workflows. Why AI still needs human judgment for decision-making and contextual reasoning – and how continuous improvement with AI creates real competitive advantage.

Software Communication Gaps: The Hidden Foundation

"Teams don't struggle because they lack talent or tools. They struggle because they lack a shared language." How communication breakdowns between business and engineering cause delays and failures – and the move from lengthy documentation cycles to rapid iteration. Treating requirements as discoveries rather than fixed specs, using AI to accelerate feedback loops rather than replace clarity, and building continuous alignment through frequent validation instead of perfectionist upfront specs.

Your Team Isn't the Problem – the System Is

How organizational systems – not people – create delivery bottlenecks. The breakdown between business and engineering functions, the dangers of starting too many initiatives at once, and how cross-functional teams improve workflow. A flow framework that balances features and technical debt, plus counterintuitive approaches to planning – drawing on 25+ years scaling engineering teams at companies like Uber.

Fixing Business–Tech Communication

How misalignment between business and engineering creates bottlenecks and accumulates technical debt. Aligning business objectives with engineering capabilities, why agile implementation often underperforms in practice, the real cost of technical shortcuts, and how to identify the actual delivery impediments – not the symptoms everyone is busy treating.

Balancing Features and Technical Debt: Effective Engineering Practices

Battle-tested advice for scaling SaaS teams, streamlining delivery, and maximizing developer happiness. Counterintuitive strategies for improving software output, optimizing technical debt, rethinking backlogs, and harnessing new mental models – drawing on experience at startups and tech giants like Uber.

Why Software Development Sucks – and 7 mental models to help fix it

Lead Editor Shane Hastie talks with Thanos about why teams struggle with software delivery. A shift in mental models and a four-step framework to systematically improve software development by focusing on bottlenecks, balancing different types of work beyond feature delivery, and investing 20–30% of effort in improving how the team works.

Transforming Software Development

How to avoid common pitfalls and embrace agility

Helping software teams deliver features faster and with higher quality. The pitfalls of over-planning, the value of agile principles without rigid ceremonies, and the importance of team communication and iterative development – with a focus on tailored coaching, practical frameworks, and mental models.

Surviving the Software Apocalypse – AI, Agile, and Good Engineering

With Frank La Vigne, Andy Leonard, and AI BAILeY: AI's impact on software engineering. The risks of "vibe coding," shifting bottlenecks, and why fundamentals still matter. Seven mental models, strategies for working with AI tools, and balancing efficiency while keeping teams sane and productive.

Scaling Startups & Tackling Tech Debt

Ashutosh Garg interviews Thanos – software delivery coach, fractional CTO, holder of seven software patents – on the critical factors behind engineering success in startups and scaleups. Managing tech debt, aligning technology with business outcomes, scaling engineering teams, navigating build vs. buy, and fostering culture in the age of AI.

When Output Doesn't Equal Progress

Why planning more often leads to less progress. What non-technical leaders need to ask their tech teams. How to find your team's bottleneck – and why that changes over time. The four stages of becoming a high-velocity software team. For founders, product leaders, and innovation execs frustrated by slow progress.

From Burnout to Breakthrough: Building Better Engineering Teams

Lessons from startups on scaling teams, debunking productivity myths, and introducing the ABCD framework. Balancing work types, avoiding burnout, and rediscovering joy in software – with personal favorites and advice. Ideal for startup founders, engineering leaders, and anyone interested in team health and software delivery.

Story of a Fractional CTO

Insights on improving software delivery and balancing work with personal life. The flexibility and value of a fractional CTO business, lessons from scaling Uber's bikes and scooters, and the importance of cross-pollinating ideas from different clients.

Ditch the Ticket Factory Mentality

The secrets of building high-performing, happy engineering teams. Drawing on 25+ years as a fractional CTO and engineering coach.

Business Lessons From Uber

A conversation about optimizing software development and engineering teams for startups and high-growth companies – drawing on 25+ years of technology leadership and lessons from Uber's growth.

Engineering Culture, Operational Excellence & Designing for Scale

A panel with Shibani Sanan (CTO @ Ladder) and Rakesh Rajan (VPE @ Rippling) on lessons across large companies and startups: scaling systems and platform strategy to encourage speed and innovation, minimizing dependencies, and shaping culture for engineering and operational excellence – manager expectations, production operational reviews, rewarding excellence, prioritization.

Architecting for Ambiguity

With CircleCI CTO Rob Zuber: the role of architecture in the face of ambiguity. From identifying the things you do know to designing systems centered around change. Domain understanding, business focus, DDD, system evolution, technology choices, and putting energy into the most impactful decisions.