Post

Quitting programming as a career right now because of LLMs would be like quitting carpentry as a career thanks to the invention of the table saw.

LLMs strike me, strictly from a development perspective as a pretty shit tooling for anyone who has written plenty of their own tools across multiple domains. But, lots of devs never bothered or bother to learn how to write tooling.

Oddly enough one of my favorite applications of them is writing personal tools - it's a great low-stakes way to explore the edges of what they can do I've got more than 100 of those now tools.simonwillison.net/colophon

Let's not confuse tools with modules. Different paradigm, and a tool never exists inside the end product. A precast concrete form isn't a tool, the machine that makes whatever precast form you want with dimensional inputs is. It's an interesting set, but low stakes tell us nothing about LLMs.

High stakes r what a bunch of us play for, and right now its high stakes game is trash. And it's competing against decades of tool history that already exist and re-exist to chunk out entire deployable/functional applications for hot customization to exact business requirements in a button press.

I want a TTC (talk to code) system as much as the next architect, but I don't need a drunk stenographer.

Here the thing: we have a very valuable system for that right now - but it's really hard to learn to use effectively I saw LLMs compared to guitars recently: you don't pick up a guitar, twang it for five minutes, get crap results and announce "guitars don't work! All hype no substance"