![\"My](\"https://media.stanko.io/variants/articles/becoming-a-photographer-tIKMwUVuHnHG/20260601_191028.jpg/1200w.webp\")
Last week the topic on everyone's mind seemed to be the future of programming.\nAll my friends were talking about it, people I follow were talking about it, and I was\nthinking about it as well. Then David's (DHH's) Rails World keynote\nturbocharged the conversation.
\nHis talk didn't come as a surprise to me. I was a week into rewriting HEY in Rust\nduring Rails World. And "Pencils down" only codified how we'd been working for months at\nthat point.
\nDavid is right. Like it or not, we programmers, like painters before us, are slowly\ngoing to disappear. AI, like the camera, completely changed the game. You can sulk about\nit, or you can pick up a camera, start learning, and become a photographer.
\nMy favorite photo this year, taken one evening in the Soča Valley
\nI was skeptical of AI and vibe coding. My initial dabbling with it didn't\nturn out that well. The agents needed a lot of hand-holding\nto produce a decent result. But the models improved at an incredible pace, and I got better at employing\nthem, learned their limitations, and learned how to express what I wanted.
\nFor me, the first real test for this new way of working was HEY CLI.
\nRob and I built it - the CLI, TUI, and the\nsupporting API, SDK, and\nActionCable client - over the span of a week while\nhe was traveling, and while I was shipping and polishing a major pricing change for Basecamp. It's\ncompletely vibe-coded. No human has seen any of the machinations in the code beyond the initial\nproject setup - and it worked out!
\nSomething clicked for me on that project. I suddenly realized that my only limit now was my\nimagination.
\nJason joined us late in the week to turn our programmer art\ninto something delightful. He did wonders in just a day - in a completely foreign medium (ASCII art),\nin a programming language he doesn't know, in a codebase no human has ever read.
\n![\"Initial](\"https://media.stanko.io/variants/articles/becoming-a-photographer-tIKMwUVuHnHG/hey-tui-email-initial.png/1200w.webp\")
Initial version of the email TUI
\n Final version of the email TUI
\nThat got me thinking: "Maybe I could design the calendar?"
\nI had a vision for what the finished calendar TUI could look like, so I gave it a go.
\n![\"Initial](\"https://media.stanko.io/variants/articles/becoming-a-photographer-tIKMwUVuHnHG/hey-tui-calendar-initial.png/1200w.webp\")
Initial version of the calendar TUI
\n Final version of the calendar TUI
\nDesigning the calendar was challenging. There were dead ends and abandoned ideas, but I got it done,\nI'm very happy with it, and I leveled up as a designer.
\nMy programming skills helped me along the way. I caught things that wouldn't work and\nguided the agents towards better solutions. I didn't need to write the code myself, but knowing\nhow software works still made me better at getting the result I wanted. And the same was true for\ndesign. The more I learned about typography, layout, and terminal interfaces, the more\nthings I could imagine trying.
\nAI removed the speed limit, but it didn't remove the limits of my imagination. The more you\nknow, the more you can imagine.
\nWalls between previously strictly defined roles have broken down: programmer, ops, designer, QA,\nmobile, web. This doesn't mean expertise is useless. Quite the opposite. A lot of what I learned\nover the years carries over and helps me see possibilities, problems, and tradeoffs\nI otherwise wouldn't. Merlin Rebovic gave a great talk about that.
\nBut knowing a bit of everything gets you much further today than being excellent at one or two things.\nEvery new skill gives you another way of thinking, another set of things you know to look for,\nand, most importantly, more things you can imagine. The future needs a more even blend of skills.
\nWhat if I told you that the photo above is the third shot out of five? Would that take away from the photo?\nIs it somehow tarnished by not being perfect on the first try? By the two photos before and after it?
\nOf course it isn't. Nobody looks at a photograph and asks: "Yes, but how many bad exposures did you take?"
\nMisfires, variations, and riffing are part of the process. It takes taste to pick out the best one and\nto polish it up.
\nIt's the same when working with agents.
\nWe used to turn an idea into code, then meticulously polish that code to excellence, and ship it.\nEvery idea had to prove its place; every line of code had to be worth the time it took to write and\nthink about it. Writing code used to be expensive, but it isn't anymore!
\nNow I can turn an idea into something real in minutes, play around with it, get a feel for it, and then\niterate on it or throw it away. The first attempt will probably be rubbish. That's okay. Every attempt\nand iteration teaches me something about where I want to go next.
\nThere will be false starts, rabbit holes, and bugs. There will be things that fall through the cracks.\nExcellence doesn't have to happen on the first try. It can be eventual.
\nI can try five ideas in the time it previously took me to prove just one. Four might not work out. But,\njust like the four photos you never saw, that doesn't diminish the one that worked.
\nThe goal is still excellence. We just don't need it at every step of the way anymore.
\nIf I'm no longer writing the code, what exactly am I doing? If you ponder that question, let me\nask you another one: Do civil engineers do engineering?
\nMy mom is a civil engineer. I have tons of memories of her at her giant drawing table with rice paper,\nrulers, pens, and razor blades, designing people's homes. With her pen she dug trenches, laid rebar,\nset walls, and picked the type of concrete to use without ever picking up a shovel. She was doing\nengineering. She was solving hard problems with hard constraints. The fact that someone else picked\nup a shovel, cut the rebar, set up molds, and poured the concrete doesn't take that away from her.
\nSo don't conflate writing code with engineering.
\nWith the agents pouring concrete, we can now focus on the thing as a whole. Not just how to\nimplement it, but how to design it, test it, deploy it, make it accessible, bring it to other\nplatforms, announce it, promote it, and charge for it. Instead of designing walls, we'll design\nhomes.
\nProgrammers will disappear, but engineering software won't. It will morph into something broader,\nsomething that's a little bit of everything. We have to become makers.
\nPicking up a camera won't instantly make you a photographer. Most of us walk around with a\ngreat camera in our pockets, yet few of us are actually good at using it.
\nIf you take a single picture, compare it to the subject, and\nconclude "this is rubbish," that doesn't necessarily mean the camera is bad.\nYou have to learn how to use it. Learn its limitations and how to work around them.
\nPhotography is also a skill. It has to be practiced, explored, and honed.
\nLike painters in the 19th century, we are in uncharted territory. Nobody really knows what\nthey're doing or what being good at photography even means. We're all exploring this new\nspace and trying to figure things out, some with more success than others.
\nThere's only one way to find out where this goes: pick up the camera.
","headings":[{"level":1,"text":"Becoming a photographer","id":"becoming-a-photographer"},{"level":3,"text":"The perfect blend","id":"the-perfect-blend"},{"level":3,"text":"Eventual excellence","id":"eventual-excellence"},{"level":3,"text":"Do civil engineers do engineering?","id":"do-civil-engineers-do-engineering"},{"level":3,"text":"Closing thoughts","id":"closing-thoughts"}]}}