Programming peaked

Summary

Programming peaked by Samir Talwar Tuesday, 25 November 2025 at 09:00 CET I remember my first job vividly. It helps, of course, that I still consider many of the people I worked with friends, and I know some of them even still read this blog. (Hi!) I also think it might have been the beginning of the end. At least, as programming is concerned. Programming in 2025 It’s 2025. We write JavaScript with types now. It runs not just in a browser, but on Linux. It has a dependency manager, and in true JavaScript style, there’s a central repository which anyone can push anything to. Nowadays it’s mostly used to inject Bitcoin miners or ransomware onto unsuspecting servers, but you might find a useful utility to pad a string if you need it. We don’t write the JavaScript, of course. We ask an autocorrect machine to make it up, and complain at it until it generates something plausible enough. Often, it does, and it only installs a malicious package 20% of the time. 30%, tops. Fortunately, when we do need to make manual changes, our editor has our back. The most popular is “VS Code”, which needs only a few gigabytes of RAM to render the text. It ships a web browser, because everything ships a web browser. It can also perform fancy refactoring techniques such as renaming a variable (in a single file). In order to test our application, we build it regularly. On a modern computer, with approximately 16 cores, each running at 3 GHz, TypeScript only takes a few seconds to compile and run. Once our work is done, we create a “pull request”. This is a way of emulating open-source development inside a single company, which as we know, is the only way to work. Typically, this means that the code is downloaded and built on another computer, and then several hours later, a colleague will come along and ask to change a few words. Once we change these words, the computer builds everything again, and then the next day, the same colleague will allow the code to be merged into the mainline. Once...