The Blank Slate

Four posts about what happens when a capable model meets a real problem and hands back something polished, confident, and wrong for you. It starts with the blank slate, because that's where everyone starts: a machine with broad knowledge and zero context on your corner of the world, filling every gap you leave with the internet's average. It ends with the suit, and the question nobody asks when they open the app. Not which rung are you. Which rung did you hire it to be?

The argument is one sentence, and it's the first line of Part 1: the model isn't the test. You are. Give it specific thinking and you get your thinking back, amplified. Give it mush and you get beautifully formatted mush. Most people can't say why the answer is wrong, because saying why takes the one thing they never built: a legible model of their own work. "AI sucks" is what it sounds like when someone reads a printout of their own vagueness and doesn't recognize the handwriting. We've seen this movie. Agile didn't fail. Shops bought the ceremonies, refused the one idea holding the building up, and blamed the framework when the pain showed up. Same script. New tool.

Read it in order. Part 1 holds up the mirror. Part 2 gives you the test for what's load-bearing in anything you've been certified in, and what's drywall. Part 3 puts words to the four kinds of people in your building, and which one the machine just repriced to zero. Part 4 is the operator's manual, and it's for you, not the machine. Each part stands on its own. Together they make one argument, and it's about you, not the tool.