What Kind of Engineer Does Aaron Levie Set Aside?

Aaron Levie sets aside the top engineers who bring deep taste and incredible judgment and treat code as art as much as science. For most of the world, code is a utility. Its value has been to automate work and to put up an interface so somebody can press a button and move to the next step. Telling an agent to generate an entire back-end or front-end is not only acceptable, it is preferable, because that build was the thing blocking the work from moving forward.

Slop stays a fair label for a while, because taste in front-end design and in systems still matters, and vulnerabilities in the code are still unacceptable. A presentation carries a different association. The audience is deciding whether the person can be trusted to execute, deliver the result, or understand the topic. A financial model already skips that test. It can be generated by a macro, the person showing it did not personally compute every figure, and the conversation still happens around the model. A strategy deck has not reached the same standing.

The open questions are what the person's role is and what the content is a proxy for: how much the person knows, or what they can go and execute on. Society might spend the next three to five years cranking through the mess and landing on the other side.