Post

This image from my blog post earlier this week really seems to be unexpectedly resonating. With Claude Code, our total project time is way down, but how engineers spend their time is very different. More architecture, more QA, less coding. www.geocod.io/code-and-coo...

11 reposts56 likes

What I'm wondering here is what is the effect on post-release productivity? Generating code is generally 10-15% of the work in the software lifecycle. Stopping the analysis at QA ignores the long tail of maintenance and improvements etc etc and whether the code is as valuable depends on that.

That's a good question. It's just a simple graphic regarding getting to the point of successfully being in production (I include any post-prod fixes in there), but not overall lifecycle.

It's only been ~6 months of us actively using Claude Code on a daily basis, but so far seems to make maintenance easier. Same story from other founders: people are talking about huge refactors that would have previously taken months or a year now being cut down to weeks

Well that’s the question isn’t it? Maintenance often done by different people and I don’t believe it’s been shown yet how the quality of the codebase that’s generated compares to human generated code as regards long term maintenance.

It seems to me you can use automatic software development to build very different code bases in terms of style. Sure you want to exit and run you can make a terribly unmaintained mess. That does not have to be the case. Also I think there will be incentives not to do this.

the bigger question we are thinking about right now is code base and product complexity. When you can suddenly ship everything you've ever dreamed of, that creates a lot of complexity

Basically "technical debt on steroids". It's true that history shows that negative signals from things being unmaintainable/endemically unsafe are not strong enough incentives in an environment of crazy growth (and boy, we are heading for a big one). 👇

yeah, I was only talking about that this week: Normally v2 would gradually reveal itself as the v1 was developed. Now with AI, I can spin up a v1 of something in hours instead of weeks but that means I've had no time to think about what v2 might look like.

interesting. I feel like with rapid prototyping and how AI makes us far less precious about code, we're getting to those future versions earlier

Still surprised by how big the response has been to this post (both good and bad, lol), and seriously nailed home the point for myself how those of us in companies using Claude Code with custom tooling are seriously in the minority, lots of people rodeoing it out there with so-so results

The shortened project lifecycle is absolutely the result of our custom tooling shared across the team, and people/orgs without that aren’t going to have those kind of results ICYMI @tjmiller.bsky.social’s excellent blog post on our Claude Code tooling www.geocod.io/code-and-coo...

geocod.ioHow we use Claude Code - GeocodioClaude Code is only as good as the context you give it. I've been building out a custom setup with skills, hooks, and MCP servers that's turned it into a genuine productivity multiplier for our Larave...