I'm a product manager, and a lot of the things I see people do wrong is because they don't have any product management experience. It takes quite a bit of work to develop a really good theory of what should be in your functional spec. Edge cases come up all the time in real software engineering, and often handling all those cases is spread across multiple engineers. A good product manager has a view of all of it, expects many of those issues from the agent, and plans for coaching it through them.

▲

nevertoolate 5 hours ago | parent [-]

Poe’s law is strong with this one

	▲	Schiendelman 5 hours ago \| parent \| next [-]
		Tell me more! I'm trying to figure out how you got that.
	▲	tristor 4 hours ago \| parent \| prev [-]
		I think that's an incredibly reductionist and sarcastic take. I'm also in Product, but was an engineer for over a decade prior. I find that having strong structured functional specifications and a good holistic understanding of the solution you're trying to build goes a long way with AI tooling. Just like any software project, eliminating false starts and getting a clear set of requirements up front can minimize engineering time required to complete something, as long as things don't change in the middle. When your cycle time is an afternoon instead of two quarters, that type of up front investment pays off much better. I still think AI tooling is lacking, but you can get significantly better results by structuring your plans appropriately.