|
|
|
|
|
by onion2k
129 days ago
|
|
That's really simple - actually writing the software has never really been the hard part in most SaaS apps. So long as you're moderately disciplined and organised it's easy to build what most SaaS apps are e.g. a CRUD-app-with-a-clever-bit. The clever bit is the initial challenge that sets it apart from the rest, but encoding that in software has never really been that difficult. Having the ideas necessary to know what to write is where practically all the value lies (caveat: there is value in doing the same as someone else but better, or cheaper.) AI can help with that, but only in so much as telling you the basics or filling in the blanks if you're really stuck. It can't tell you the 'clever bit' because that is by definition new and interesting and doesn't appear in the training data. What this means is that at some point Anthropic will be able to prompt Opus to clone Jira and never pay an Atlassian bill again. Opus just needs to figure out what Jira is first. It's not there yet. |
|
Bang on, and Jira is the perfect example! Because Jira isn't a bag of features: Jira is a list of features and the way they fit together (well or poorly, depending on your opinion).
That's the second-order product design that it's going to take next-gen coding AI workflows to automate. Mostly because that bit comes from user discovery, political arguments, sales prioritization, product vision, etc. It's a horrendous "art" of multi-variable zero-sum optimization.
When products get it right (early Slack) then it's invisible because "of course they made it do the thing I want to do."
When products get it wrong (MS Teams, Adobe Acrobat, Jira, HR platforms) then it's obvious features weren't composed well.
Expect there's more than one {user discovery} -> {product specification} AI startup out there, working on it in a hierarchical fashion with current AI now.