𝔸𝕟𝕘𝕖𝕝𝕚𝕟

People tell me that using an LLM to create code will rot my programming-language skills. So? We work in a changing landscape, and agility is essential to survive. My goal is not to be the best Python (or whatever) programmer on the planet. My goal is to produce the most valuable, high-quality product in the shortest time possible. To do that, I want to use the most effective tools available. That might be a programming language, an LLM, a combination of the two, or something else entirely. Toolsets are constantly evolving. Keeping up is part and parcel of being a developer. I need to be skilled with the tools I'm using right now, not the ones I used in the past. People who rest on their laurels quickly become unemployable. I guess the difference between the critics and me is that I've never seen myself as just a programmer (though I'm pretty good at that, if I do say so myself 😄). I'm a developer. I develop products and tools. To do that, I need to know how to program, but I also need to know architecture, product discovery and refinement, systems thinking, testing, TDD, UI/UX, and a host of other skills, including communication and process improvement. Every one of those things is integral to what I do, and most of them are not impacted by the LLM at all. As for those rotting coding skills, I still need to code to use the LLM effectively. I need to read and understand the code, refactor it when needed, and write things by hand that the LLM can't or won't write. With the tool, however, I can work faster. When I moved from assembly language to C, from C to C++, from C++ to Java, from Java to Kotlin, from Kotlin to Python, the earlier skills indeed rotted away. I didn't much care. I can get them back easily enough if I need to. I'm with Sherlock Holmes, here. When Watson told him that the Earth goes around the Sun, he said that now that he knew it, he'd do his best to forget it. "What the deuce is it to me? … You say that we go round the Sun. If we went round the Moon, it would not make a pennyworth of difference to me or to my work."

The most powerful programming language of the future isn’t C++ or Python. It’s English. Jensen Huang: “Why program in Python? So weird.” You won’t write code anymore. You’ll describe what you want. If the result isn’t right, you won’t debug. You’ll just tell it to fix itself. The barrier to controlling computers is hitting zero. We’re shifting from syntax to intent. You don’t need to know how to write a script to modify a system. You need to know how to explain what should happen. Huang: “English is the best programming language of the future.” Prompt engineering is just clear communication with a new audience. How you talk to people and how you talk to machines is becoming the same competency. If you can articulate what you need clearly, you’re a developer. If you can refine through conversation, you can ship products. The coder is obsolete. The orchestrator is everything. The skill isn’t syntax anymore. It’s clarity. Knowing what to build, how to ask for it, and how to direct until it’s exactly right.

Regulating digital platforms to protect citizens, democratic debate and the rule of law is not censorship. It is responsibility.

Aerial view of Booster 18 taken yesterday.

Don’t overthink it. * host a website on Cloudflare Workers * deploy a web app on Cloudflare Workers * build a serverless API on Cloudflare Workers * set up D1 for your data, or use Hyperdrive * Automate back-ups with object lifecycles * Monitor apps using Worker metrics and analytics * Build a URL shortener using Workers and KV * Configure a custom domain with 1 click You can also learn Full Stack Cloudflare by watching videos, but build something too.

What the HECK is going on with tech? In the last week: Multiple cloud outages, x DMs totally broken, antigravity doesn't work, my watch is showing me 15 year old cal events, mac OS is a mess, email is spammed to hell and every nerd on here is talking like new AI is the second coming