> nearly 100% of code would be written with AI in 2026

I feel like this is kind of a meaningless metric. Or at least, it's very difficult to measure. There's a spectrum of "let AI write the code" from "don't ever even look at the code produced" to "carefully review all the output and have AI iterate on it".

Also, it seems possible as time goes on people will _stop_ using AI to write code as much, or at least shift more to the right side of that spectrum, as we start to discover all kinds of problems caused by AI-authored code with little to no human oversight.

Bug reports should describe the problem but often shouldn't try to prescribe a solution.

But yeah, it prevents an ineffective legislature from leading to strong-men, which does seem nice. :)

Why do people do this though? Maybe it's inevitable, but I think there was a lot of pent up frustration with the government that led a lot of people to just say "fuck it". Not really excusing it (especially for his second term), but I feel like we're reaping years and years of a dysfunctional and ineffectual congress. Not that that's an especially easy problem to solve either.

I think this also explains a lot of the frustration with SCOTUS. In-theory, SCOTUS is supposed to just interpret and flesh out the policies decided on by congress. In practice, congress doesn't really do anything, and people started depending on SCOTUS's ability and willingness to make far-reaching and impactful decisions. Now a more conservative SCOTUS isn't doing that.

https://en.wikipedia.org/wiki/Touch_typing

I think they're referring to the latter.

Craft often inspires a quasi-religious adherence to fight the ever-present temptation to just cut this one corner here real quick, because is anything really going to go wrong? The problems that come from ignoring craft are often very far-removed from the decisions that cause them, and because of this craft instills a sense of always doing the right thing all the time.

This can definitely go too far, but I think it's a complete misunderstanding to think that craft exists for reasons other than ensuring you produce high-quality products for users. Adherents to craft will often end up caring about the code as end-goal, but that's because this ends up producing better products, in aggregate.

Yeah I'm aware, but as any company gets larger and has more and more traffic (and money) dependent on their existing systems working, keeping those systems working becomes more and more important.

There's lots of things worth protecting to ensure that people keep using your product that fall short of "lives are at stake". Of course it's a spectrum but lots of large enterprises that aren't saving lives but still care a lot about making sure their software keeps running.

Even if we ignore criticality, things just get really messy and confusing if you push a bunch of broken stuff and only try to start understanding what's actually going on after it's already causing issues.