AI is _certainly_ not useless and definitely not bad, far from it, but if I could snap my fingers and make it disappear, I'd do so in a heartbeat.

Writing code is my favorite thing to do. Digging into a problem and getting into the flow is my favorite thing ever, and it seems that the world is completely hell-bent on taking this away from me.

I can already hear all the usual responses: "but you can still write code in your spare time," "you were never paid to type anyway," etc etc etc. That's all true, but it doesn't change the fact that writing code in your spare time and being paid to write code for the plurality or even majority of your waking hours are two completely different ways of life. And yeah, there's a lot more to being a software developer than just typing, but the quality of the time spent has completely and utterly changed. It's quickly becoming unrecognizable compare to even just a few short years ago.

I am of the belief that how you spend your days is how you spend your life, and given that so many of our days are now spent doing completely different activities, with a completely different, much "louder" quality to them (I find prompting to be almost _socially_ exhausting, and hate that it more or less completely destroys the ability for oneself to enter a flow state), I think it's completely fair to say that AI has radically changed, or perhaps even ruined, our lives, or at least our livelihoods.

And in my specific case, I already completely changed careers once. Long story short, I was a lifelong musician and well on my way to becoming a successful film/TV/video game composer before I developed hyperacusis. Going through that was horrific. I consider myself extremely lucky to have found a vocation and avocation in programming that, against all odds, I love even _more_ than making music. And once again, I feel that I might just have to change careers. Again.

So yeah. I'm not naive enough to think that it's going to go away. But my life and work were 100% better before it, no question.

I've been feeling this way about web dev for a while now, and sometimes look at C++ devs with jealousy, wishing that the crazy amount of memorization/varied standards/rough maintenance/high difficulty I experience were only limited to the language that I write.

That said, you are correct that it has nothing to do with Windows (and I never said that it did).

XDG has nothing to do with X11. XDG stands for "Cross-Desktop Group," and is designed specifically for any Unix or Unix-like operating system, which includes macOS.

And not once have I ever felt that these so-called intersections were anything other than contrived.

Of course we can interface with music from a mathematical perspective, but that doesn't mean that we should or that there's anything particularly illuminating to gleen from doing so.

Beyond the very basic math (honestly even that's perhaps too strong a word -- just because something is expressed in numbers doesn't make it _math_) of time signatures and some harmonic concepts up to maybe some of Slonimsky's work, doing so is IMO a fool's errand that exists only to fill space on a TEDx stage.

Obviously there are tons of tools and systems building up around LLMs, and I don't intend to minimize that, but at the end of the day, an LLM is more analogous to a tool such as an IDE than a programming language. And I've never seen a job posting that dictated one must have X number of years in Y IDE; if they exist, they're rare, and it's hardly a massive hill to climb.

Sure, there's a continuum with regards to the difficulty of picking up a tool, e.g. learning a new editor is probably easier than learning, say, git. But learning git still has nothing on learning a whole tech stack.

I was very against LLM-assisted programming, but over time my position has softened, and Claude Code has become a regular part of my workflow. I've begun expanding out into the ancilary tools that interact with LLMs, and it's...not at all difficult to pick up. It's nothing like, say, learning iOS development. It's more like learning how to configure Neovim.

In fact, isn't this precisely one of the primary value propositions of LLMs -- that non-technical people can pick up these tools with ease and start doing technical work that they don't understand? If non-technical folks can pick up Claude Code, why would it be even _kind_ of difficult for a developer to?

So, I'm with the post author here: what is there to get left behind _from_?

I know everyone thinks they're going to just kill it, but I don't see it. Apple's move under Tim Cook has been to exhaust supplies (see: filling the Intel Mac Pro chassis with air and not updating the CPU), letting people predict its death (see: 2013 -> 2019 Mac Pro silence), and then redesigning it into something people want while utilizing it as an opportunity to segment specs across their SKUs.

The Studio will remain the high-powered creator machine, whereas the Mac Pro will be retooled into an AI beast.

In my own work, this often looks like writing the quick and dirty version (alpha), then polishing it (beta), then rewrite it from scratch with all the knowledge you gained along the way.

The trick is to not get caught up on the beta. It's all too tempting to chase perfection too early.

Give me some life and color and personality, damn it.