alt Hacker NewsAs a SaaS author, I couldn't agree more. That's how I see my work: the value is not in the code (AI can code better than me at this point), nor even in the software architecture (AI is just getting to the point where it will get better than me). It's in deciding what to build and what not to build, defining the overall character and vision of the product, looking at each screen and thinking "how does this help my customer do their job".
This, unfortunately, takes time, as one has to restart many times because of ideas that turned out not to be as great as one had initially thought. And it results in software that is called "opinionated", and often does not follow what the "industry" does.
Replies
There’s still inherent value in people that can write code better and make architecture better than LLMs; even if you can’t.
Assuming high-quality models are around for the foreseeable future, and at this point I’m convinced that they will be. I think we’re moving into an era where breadth and hybridization of skill sets will become more valuable than pure technical depth. We’ll need more “wide T” shaped people that can exercise good UX, product, and architectural judgement and fewer “long T” shaped technical purists.
This puts large orgs at a disadvantage because they are built to coordinate work across a collection of narrowly scoped roles and keep people in their lane, so they aren’t built to hire for and leverage broad skillsets.
> the value is not in the code (AI can code better than me at this point), nor even in the software architecture (AI is just getting to the point where it will get better than me)
The lies of this decade. Hopefully we will heal sooner than later
> the value is not in the code (AI can code better than me at this point), nor even in the software architecture (AI is just getting to the point where it will get better than me). It's in deciding what to build and what not to build, defining the overall character and vision of the product,
Defining what to build in enough details is how you get the business logic nailed down (aka essential complexity, aka the domain in DDD). Code is just formal writing and architecture is there for maintenance (a program can be in a single file).
Sure there are accidental complexity like the intricacies of the tech, but those are actually explained very well in the docs.
> it's in deciding what to build and what not to build
Unfortunately, humanity seems like a race destined to kill itself. People are more interested in how much they hate their neighbor or feel excited about an advertisement than anything meaningful. such a society has no basis for stable governance.
If AI can write better code and design better architecture, why can’t it make better product decisions? I don’t see how they are fundamentally different