

Civilised countries use events like this as a vehicle (no pun intended) to build infrastructure - like public transport - for the event that will then be a public good after.


Civilised countries use events like this as a vehicle (no pun intended) to build infrastructure - like public transport - for the event that will then be a public good after.


Republicans.


It’s still the case that users from the US dominate most online spaces, so illiteracy is to be expected. I wouldn’t consider it suspicious on its own.


LibreOffice still hasn’t managed to sort out making the UI scalable on Wayland, so you’re stuck with either needing a magnifying glass to see the icons or you have to stand in the next room over and nothing in between. Given how many years they’ve had to work on that, I feel like the odds of them developing a working web UI in my lifetime are pretty slim.


It’s not uncommon. Rivian, Rimac, and various Chinese cars all have IWD (Individual Wheel Drive.) For a rather longer time, trams have been running with stub-axles and individual motors for decades.
He may be dead right, and unduly pessimistic at the same time.
The industry massively overhired relatively unskilled people who believed the job was “writing code”, for a few decades; those people got by thanks to Stack Overflow and the fact that most of the code that needed writing really didn’t need much skill anyway. There’s very little innovation or engineering in most business platforms - a couple of decent architects and an army of code monkeys can deliver most of the software that’s needed. We also developed programming languages and frameworks that made it much easier for the unskilled developers to be productive.
Sad to say, these are the people now loudly wailing about the iniquities of AI. If you thought churning out code was the profession - you absolutely should be very concerned that AI will replace you - it will. But if you realised that code was only ever a side effect of the job, which was applying computing to solve problems - you have little to worry about. AI is just a new tool to do it, and is no more a threat than optimising compilers, mamaged runtimes or IDEs were.
When I started my career, I wrote assembly code by hand for platforms that barely even had an operating system. Then C. Then Java - and as far as I’m concerned, every programming language since then has pretty much had training wheels permanently attached… For the last few years, I’ve preferred Rust, although the job has been more about developing architectures for others to implement than coding myself. But my expectation is that I’ll end my career writing instructions for AIs to implement; and that’s absolutely fine. The job didn’t change, just some of the intermediate representations I had to write to do it. The profession will probably go back to look more like the one I entered - fewer people doing it, but with more formal education in computer science, and much less “coding”.
Which is not to say I don’t think there’s anything to worry about for the profession, there absolutely is. How the hell we identify the future senior engineers with the actual skill and aptitude required, when there are no junior roles to provide the necessary apprenticeship - and when the education system is struggling to adapt to AI use in class - is a massive and fundamental problem. That’s what keeps me awake at night, not people who think writing CRUD APIs in C# is a divine gift.