limited·by·sleep
$ cd ~/published

You won't understand AI until you've used it yourself

There's an entire industry now devoted to telling people what to think about AI, and it's easy to read enough of it to feel like you understand the thing. You don't. Not until you've used it yourself.

Reading feels like progress. You finish another thread, another newsletter, and you walk away convinced you're keeping up. But the understanding I actually trust came from doing the work, not from reading someone else's account of it.

I use it to prototype ideas I'd never have had time to build before, and just as often to think, as a sparring partner that pulls my arguments apart or a coach when I'm working through a decision. None of that is something you learn from a summary.

And it isn't a developer thing. The fastest way to understand what these tools can do is to point one at something in your actual week.

Ask it how to cut your meetings next week. Get it to help you plan next week's meals. Have it explain the evolution of cats in a way a child would follow, or why water expands when it freezes. Ask it to map out a realistic path to your next promotion.

None of those need code. All of them teach you more in ten minutes than another week of reading will.

So if you feel behind, stop reading about it for a bit. Try something, anything. Doing is the real work, and it's the only part that teaches you.

follow via rss