I'm a programmer, been coding professionally for 10 something years, and coding for myself longer than that.

What are they talking about? What is this "devaluation"? I'm getting paid more than ever for a job I feel like I almost shouldn't get paid for (I'm just having fun), and programmers should be some of the most worry-free individuals on this planet, the job is easy, well-paid, not a lot of health drawbacks if you have a proper setup and relatively easy to find a new job when you need it (granted, the US seems to struggle with that specific point as of late, yet it remains true in the rest of the world).

And now, we're having a huge explosion of tools for developers, to build software that has to be maintained by developers, made by developers for developers.

If anything, it seems like Balmers plea of "Developers, developers, developers" has came true, and if there will be one profession left in 100 year when AI does everything for us (if the vibers are to be believed), then that'd probably be software developers and machine learning experts.

What exactly is being de-valuated for a profession that seems to be continuously growing and been doing so for at least 20 years?

We're clearly seeing what AI will eventually be able to do, just like many VOD, smartphone and grocery delivery companies of the 90s did with the internet. The groundwork has been laid, and it's not too hard to see the shape of things to come.

This tech, however, is still far too immature for a lot of use cases. There's enough of it available that things feel like they ought to work, but we aren't quite there yet. It's not quite useless, there's a lot you can do with AI already, but a lot of use cases that are obvious not only in retrospect will only be possible once it matures.

I've been using VSCode's Copilot with Claude Sonnet 4 and find it to be terrifyingly competent running 8 hours a day costing ~$10.

I am developing techniques to keep it moving forward producing code and fast. First, prompt engineering like "write clean, simple, and elegant code." Second, I use TypeScript very strictly which helps. Third, the models are amazing at producing very simple test units which will be important in the fifth. Fourth, I use techniques like "look for opportunities to refactor pure functions in the file and put them at the top of file" or "look for opportunities to refactor pure function and put them in shared utils.ts file." Fifth, every hour or so, I will have the agent simplify and clean the code and with complete test coverage both unit and integration as longs as they all pass .... good to go.

This is a process and it is the same every time. So now I'm thinking about how do I write code to automate these steps into an automated process. For example, I keep using the same pattern of steps to solve hard debugging problems which I'm going to leave out of this conversation now. If I can create a process in code, I'd be one step closer to complete automation coding.

The patterns are emerging. I strongly believe in 12 months these systems are going to be able to write extremely complicated programs with very little input from the human in the loop.

Meat, bread, eggs, dairy, onion, herbs, spices.

Industrial food has a lot of things which are much less recognizable as food.

Degrees of separation from something alive which I'd like to eat to the ingredient matters to plenty of people.