Explaining to business people why building software is still hard
Thread
Unofficial Hacker News client; not affiliated with Y Combinator.
Explaining to business people why building software is still hard
Unofficial Hacker News client; not affiliated with Y Combinator.
miranaproarrow · · focus · HN ↗
My job is to wire to our backend data, and a lot of these wiring require me to be in there and actually think about the features. These take time, and I just haven't figure out a way to speed this process up with Claude.
godwinson__4-8 · · focus · HN ↗
Why won't smarter and cheaper models in the future be able to automate this part for your manager as well? How novel is the feature set? Is it he has a knowledge gap or the model is incapable of something? What expertise are you bringing to bear that is beyond the scope of a future harness/model? Why wouldn't such a model simply fill in the blanks for your management, perhaps observing a diff of whatever you did? How do you verify the correctness of your thinking? Why could a future model not replicate this process?
I am just very puzzled by these sort of takes as we approach the end of 2026.
miranaproarrow · · focus · HN ↗
The only difference right now between my manager getting this claude design web app to production are the infrastructure and interfacing with it.
To get to prod it has to go through our monorepo pipeline, which currently requires using a cli, using a cli/command prompt requires using terminal, getting claude to use terminal also requires you to even know what a terminal is and spawning claude in there. Steering claude to do all that without knowing what or how to use a terminal is, and setting up your environment still all requires some technical knowledge or the language to tell claude to do that.
That's just getting to production. What about getting the claude design which is in a web environment without any context of all that monorepo with all its backend services. So all the interactivity that are all faked or mocked. Has to be converted to a real react components that's actually wired to the Rest API. How do you get the manager to speak to claude to do all that, with claude only being on the claude design harness?
What if manager designed a new feature that the backend service doesn't support? now your asking to make changes on the backend too.
So I think your points are valid that sure we may get to this at some point. But how exactly without the manager having to learn some technical language of steering claude and the infrastructure to support it.