Menlo Ventures partner Deedy Das warns of a fundamental shift in the developer profession caused by the aggressive adoption of AI tools. In his view, the industry is facing an "identity crisis," where the engineer's role is shifting from direct code writing to "botsitting" — overseeing massive volumes of machine-generated output.
What Happened
The industry is seeing a transition toward a practice called "tokenmaxxing," where the use of AI for code generation is becoming widespread. This creates a deep divide in the professional environment: some engineers rely entirely on automation, while others, acting as "craftsmen," are forced to take on the primary burden of verifying, debugging, and understanding the generated code.
Context
This transformation is occurring as code generation becomes a cheap commodity. However, the cost of ownership, verification, and maintenance of this code is growing exponentially, as the process shifts from creation to the quality control and security of AI output.
Why It Matters for the Industry
For the IT industry, this means that the primary bottleneck in development is no longer writing functions, but the human ability to control quality. Companies risk facing a sharp increase in technical debt and bugs if quality control processes are not adapted to handle the new volumes of machine generation.
Why It Matters for Users
Developers need to change their approach to learning and working: value is shifting from syntax knowledge to high-level expertise, architectural understanding, and deep analysis (debugging) skills for third-party or machine-generated code. Specialists unable to move beyond simple automation usage risk losing their relevance.
What Is Not Yet Known / Limitations
There are varying interpretations of the risks: while AI architecture experts focus on structural issues and technical debt, other analysts emphasize the broader transformation of professional identity.
Sources
Author
Look at AI, Editorial Team