[supern0va]

>Anyone can be an "ideas guy".

I think there's way more nuance to this than you're willing to admit here. There's a significant difference between the guy who thinks "I'm going to make X app to do Y and get loaded." and the person who really understands the details of what they want to create and has a concrete vision of how to shape it.

I think that product shaping and detail oriented vision of how something should work and be used by people is genuinely challenging, wholly aside from the lower level technical skills required to execute it.

This is part of the reason why I wouldn't be surprised at all to see product manager types getting more hands-on, or seeing the software engineering profession evolve into more of a PM/SDE hybrid.

[cgg23]

Disagree massively.

A proper PM should be moving towards owning design and marketing pieces - not production of software. Software is a means to package an experience captured by the design and communicated via marketing. It's that simple.

Most PMs don't match this description. So I understand the frustration's of engineers who have had to work with PMs.

[supern0va]

A well constructed BRD is a very large chunk of the context needed for more successful use of an LLM. You're welcome to disagree, but I've found increasingly that the work artifacts from PMs are becoming even more essential to the actual development.

If you understand the design and user experience end to end and can express that effectively in writing, that's...your agent context. Why do a context hand-off to another human, or at least why remain as silo'd as we have historically been?