Redefining the engineer's job as building guardrails is not novel — it is the same problem as making a junior engineer effective, which we never solved either.

The thing that I find interesting is that's not novel. This has been the thing we've always been trying to do forever. How do we get a junior engineer to ship code safely without breaking stuff? Right? How do we make patterns in the codebase? How do we make tests? Like it's it's all the old stuff that we've always wanted to do.