I'd be interested to see how tools like Cursor/Windsurf and even Copilot are modeling this internally. This idea seems to be a natural extension to having a hierarchy/team of agents all working on a common goal. In this case I would imagine one agent serves as the architect or reviewer, and another generates code to meet spec, and they fight back and forth until converging/diverging.

I'm currently enrolled in the OMSCS program, and so far I would call it so-so.

I joined the program because I come from a non-CS background - undergrad in math, work in an unrelated field: consulting. I'm trying to pivot into a ML Engineer career. If you want to learn ML, you're better off going through the Ng Coursera course and from there pursuing some personal projects. The primary value of the program is the ability to get past recruiting coordinators simply due to the fact I'm enrolled in CS program.

The two undergrad CS courses I took at Berkeley were more rigorous, and were superior from a skills development perspective. But at the price, the OMSCS program is definitely worth it for someone coming from a different background.