Similarly some of the molds for angentic work are reusable as long as you stay in the same general field.
We're not trying to perfectly define the problem, but rather adding barriers to so that the AI can't veer off course and drive itself down a cliff.
Especially if you're in a product house developing and improving a single product over years, creating the "mold" is even more important. You know where you've been and where you want to go so it's easier to define the technologies and systems the AI should use.
For greenfield stuff there are some parts that can be re-used between clients, but there's definitely less of it.
But I do agree that code is not the problem, defining and describing the problem is the problem =)
We're not trying to perfectly define the problem, but rather adding barriers to so that the AI can't veer off course and drive itself down a cliff.
Especially if you're in a product house developing and improving a single product over years, creating the "mold" is even more important. You know where you've been and where you want to go so it's easier to define the technologies and systems the AI should use.
For greenfield stuff there are some parts that can be re-used between clients, but there's definitely less of it.
But I do agree that code is not the problem, defining and describing the problem is the problem =)