2,772 karma · joined July 2, 2009
With the 3 and the Y they're already catering for a large part of the market demand, but a smaller model, and a stationwagon might help get it up to 80%+ of all demand.
And in practice i have more control with a coding agent than with developers as i can iterate over ideas quickly: "build this idea", "no change this", "remove this and replace it with this". Within an hour you can quickly iterate an idea into something that works well. With developers this would have taken days if not more. And they would've complained i need to better prepare my requirements.
If you check the commit log, you'll see small increments. The architecture document is what i have it generate to validate the created architecture: https://github.com/ako/backing-tracks/blob/main/docs/ARCHITE...
Other than that most changes start with the ai generating a proposal document that i will review and improve, and then have it built. I think this was the starting proposal: https://github.com/ako/backing-tracks/blob/main/docs/DSL_PRO...
This started as a conversation in Claude Desktop, which it then summarized into this proposal. This i copied into claude code, to have it implemented.
You are a lead architecture, a product manager, a lead UXer, a lead architect. You don't have 100% control over what your LLM devs are doing, but more than you think. Just like normal managers don't micromanage every action of their team.
A nice example is guitar building: there's a whole bunch of luthiers that stick to traditional methods to build guitars, or even just limit themselves to japanese woodworking tools.
But that is not the only way to build great guitars. It can be done by excellent luthiers, building high quality quitars with state of the art tools. For example Ulrich Teuffel who uses all sorts of high tech like CAD systems and CDC machines to craft beautiful guitars: https://www.youtube.com/watch?v=GLZOxwmcFVo and https://www.youtube.com/watch?v=GLZOxwmcFVo
Unfortunately, craftsmanship does not come cheap, so most customers will turn to industrially created products. Same for software.
When working with an LLM i care more about prompting it about software architecture, software UX, and the domain we're working on, than the details of the language it uses.
But most enterprise software does not need to be innovative, its needs to be customizable enough that enterprises can differentiate their business. This makes existing software ideas so much more configurable. No more need for software to provide everything and the kitchen sink, but exactly that what you as a customer want.
Like in my example, I don’t know of any software that has exactly this feature set. Do you?