The Shrinking Team That Ships More

The best time to be a software engineer is right now.

The job isn't getting easier. Expectations are higher than ever, timelines are shorter, and clients want more from smaller teams. What's changed is your leverage.

AI-assisted development is real, and the productivity multiplier is real. Though if anyone (including me) tells you one engineer now replaces five, ask them to ship something in a legacy environment first. The truth is more nuanced: the right engineer, using AI as a primary tool and not just an autocomplete shortcut, can compress timelines and cover ground that previously required a full team.

I've watched this shift happen in client conversations. Scoping discussions that used to anchor around headcount are anchoring around outcomes. Once those outcomes are defined, they want to know how many people we're bringing to execute. They expect smaller teams that accomplish more in a shorter time period. They expect us to be better thanks to the modern advances in automation and AI.

In order to be the engineers that will thrive in this new era, they'll be the ones who treat AI like a junior developer that never sleeps, never complains, and needs constant supervision.

You still have to know what good looks like. You still have to catch the mistakes. You still own the architecture decisions. You will be tempted to ask the AI if it's correct. It might lie to you. You must be able to review, consider, and critique what it produces when working in an enterprise context.

Is this code for a user base of one, you personally? Then fire away and run that app without putting the same level review and validation into it. The "blast radius" is you. You own the risk.

In the enterprise though, that blast radius is your customers, your co-workers, your shareholders.

The ceiling for what a single, skilled engineer can accomplish has never been higher. The question is whether you're building toward that ceiling or waiting to see what happens.

Ship something this week. Use every tool available. That's the preparation. Building with the tools extends your knowledge to not just the problem domain, but to an understanding of what tools perform which tasks well, and where they'll need the most human help.

🤖 AIL LEVELS: This content’s AI Influence Levels are AIL2 for the writing, and AIL4 for the images. AI Influence Level (AIL) framework