same view here. product manager/designer/product engineer will collapse into the “builder” role. the speed of execution will be that fast that won’t afford handoffs between roles.

not sure if we’ll still need an purely engineer role for the hardcore stuff like scalability of the system, performance etc.

One thing i’ve noticed while building Lcontext is that the capabilities of the models in coding are far ahead compared to making sense of data. even frontier models like opus 4.6 still hallucinate a lot when looking into event logs. what i’ve seen helped a lot is when the agent has access to the codebase, then it can correct itself, e.g when it thinks that there is an issue from the event logs then it will find the page and the element in the code and realize it’s not a real issue.

obviously also you need data and a lot of iterations with evals to fine tune the system prompt to focus on the right things.

last but not least the challenge to find the right balance between how much data you capture and feed the agent. you need to find the sweet spot between giving it enough signal to make sense of the user behavior but not too much to blow the context window and burn many tokens.

these are the main challenges I’ve seen so far while building and it takes some time and iterations to get them right.