Photoshop alternatives already exist and are cheap or free, like Affinity.
Why create a Final Cut Pro alternative when it’s so cheap from Apple?
Many existing apps can be mostly cloned by a small team over 6 months or a year, but the challenge is finding customers willing to switch. You still need to add something new and useful, then reach customers somehow.
"Many existing apps can be mostly cloned by a small team over 6 months or a year,"
I have a vision of re-imagining stuff that is currently done across 5 apps, done within one that is far simpler and with favourable economics. Most people wont figure this kind of stuff out - it requires a lot of imagination. And if done in stealth - the incumbents will be fcked.
My belief is that we are gonna see a lot of consolidation - things that used to be done across multiple apps within one. Whilst at the same time a rise in apps that do one thing really really well - think of it as being closer to the ideal product where people current face a mismatch cost. This will remove the existence of most 'general' apps - which is a good thing imo.
Is your team measuring how much of your code is being written with claude and comparing amongst the team, like what works best in your codebase? How are you learning from each other?
I’m making a team version of my buildermark.dev open source project and trying to learn about how teams would like to use it.
Different teams are using it in very different ways so it can be tough to compare meaningfully.
Backends handling tens to hundreds of thousands of messages per second with extremely high correctness and resilience requirements are necessarily taking a different approach to less critical services that power various ancillary sites/pages or to front end web apps.
That said there's a lot of very open discussion around tooling, "skills", MCP, etc., harnesses, and approaches and plenty of sharing and cross-pollination of techniques.
It would be great to find ways to better quantify the actual value add from LLMs and from the various ways of using them, but our experience so far is that the landscape in terms of both model capability and tooling is shifting so fast that that's quite hard to do.
Thanks for the feedback. I agree that it’s changing very fast, which is why my thesis is that this tooling will be needed to help everyone on the team keep up.
To help you decide if you should keep your Claude subscription, you can see how much of your code is written by Claude Code with my project (open source, local): https://github.com/gelatinousdevelopment/buildermark
I've been using a VM for claude code (probably would keep doing that as I do like how much control I have over it by doing that) but this is definitely a useful tool, I'll happily use that in the future.
The complete log of all prompts and commits is here: https://demo.buildermark.dev/projects/u020uhEFtuWwPei6z6nbN
reply