Code is a legal responsibility, not an asset
Let’s get again to first rules. As any senior engineer is aware of, software program improvement isn’t a typing contest. It’s a decision-making course of. The job is much less about writing code and extra about determining what code not to put in writing. As Honeycomb founder and CTO Charity Majors places it, being a senior software program engineer “has much more to do along with your capability to know, keep, clarify, and handle a big physique of software program in manufacturing over time, in addition to the power to translate enterprise wants into technical implementation.”
Each line of code you ship is a legal responsibility. Each line should be secured, debugged, maintained, and finally refactored. Once we use AI to brute-force the “building” part of software program, we maximize this legal responsibility. We create huge floor areas of complexity that may resolve the instant Jira ticket however mortgages the longer term stability of the platform.
Orosz’s level about 996 corporations producing copies is telling. Innovation requires the “slack” to suppose with out the fixed interruptions of conferences. Given a quiet second, you may notice that the characteristic you had been about to construct is definitely pointless. In case your builders are spending their days reviewing an avalanche of AI-generated pull requests, they haven’t any slack. They aren’t architects; they’re janitors cleansing up after a robotic that by no means sleeps.