Comment by enraged_camel
4 hours ago
>> The limiting factor at work isn't writing code anymore. It's deciding what to build and catching when things go sideways.
Actually I disagree. I've been experimenting with AI a lot, and the limiting factor is marketing. You can build things as fast as you want, but without a reliable and repeatable (and at least somewhat automated) marketing system, you won't get far. This is especially because all marketing channels are flooded with user-generated content (UGS) that is generated by AI.
Recently, I came across Erich Fromm's distinction between "being mode" and "having mode" (AI really explained it the best, would paste it here but it's somewhat long). You're, in contrast with parent post, looking at it from the "having mode" - how to sell the "product" to someone.
But you can also think what would you want to build (for yourself or someone you know), that would otherwise take a team of people. Coding what used to be a professional app can now be a short hobby project.
I played with Claude Code Pro only a short while, but I already believe the mode of production of SW will change to be more accessible to individuals (pro or amateur). It will be similar to death of music labels.
>nd the limiting factor is marketing.
Depends if you're talking about new client acquisition or expansion of existing products in order to assure your client doesn't leave.
The issue I see with this, at least in enterprise, is while we may fix some smaller plates of spaghetti, we're busy building massive tangled pasta apps that do even more.