[decidu0us9034]

Maybe for some subset of sotware (like CRM panels or something) PMs will do everything. But if you're projecting the way one sort of software (ie user-facing, business use oriented software) is developed and put to use with software writ large, then no I don't think so

[satvikpendem]

Sure, I'm just talking about 90% of software which is basic CRUD, not complex systems or microcontroller programming. In that case it's likely that just a PM could build something with LLMs.

[sarchertech]

For basic CRUD we’ve had no code solutions that PMs could have been using for decades.

The truth of the matter is that software starts as basic CRUD and then given time and users evolves into its own special snowflake. Every single system given enough time and users will become a “complex system”.

[satvikpendem]

The difference is no code tools are not flexible in the same way LLMs are. As long as PMs can articulate those snowflake requirements to the LLM then it will happily build it.

[sarchertech]

Sure for a few. But eventually the interaction of all those complex features turns it into a “complex system”.

Which as you yourself just said are not conducive to PM vibe coding.

[satvikpendem]

I'd say the majority of these sorts of tools are actually simple enough to be vibe coded, only some are complex enough to require an actual engineer building it rather than vibe coding. So in most cases it's actually a win for the PM.

[sarchertech]

Only if you’re talking about tools with very few users that haven’t been around long. In my experience the conflicting requirements and workflows that accrete over time are too complex for people to reason about without more formal methods.