From 8bf37f519ae0c23477ac2b00de6aec33d9265cee Mon Sep 17 00:00:00 2001 From: Carson Gross Date: Fri, 27 Feb 2026 14:49:25 -0700 Subject: [PATCH] more tweaks --- www/content/essays/yes-and.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/www/content/essays/yes-and.md b/www/content/essays/yes-and.md index ce36ab2d..c0b2053b 100644 --- a/www/content/essays/yes-and.md +++ b/www/content/essays/yes-and.md @@ -201,10 +201,12 @@ and you may be criticized for being slow. The work dynamics here are important prioritizes speed over understanding (as many are currently) you need to accept that and not get fired. However, I think that this is a temporary situation and that soon companies are going to realize that vibe coding at -speed suffers from worse complexity explosion issues than well understood, deliberate code does. At that point I expect -slower, more deliberate coding with AI assistance will be understood as the best way to utilize this new technology. +speed suffers from worse complexity explosion issues than well understood, deliberate coding does. -Where AI can help juniors is in accelerating the road to senior developer by eliminating accidental complexity that often +At that point I expect slower, more deliberate coding with AI assistance will be understood as the best way to utilize +this new technology. + +Where AI _can_ help juniors is in accelerating the road to senior developer by eliminating accidental complexity that often trips juniors up. As I said above, viewing AI as a useful although sometimes overly-eager helper rather than a servant can be very effective in understanding the shape of code bases, what the APIs and techniques available for a particular problem are, how a given build system or programming language works, etc.