The skill of getting familiar with AI use, how to use it, when to use, learning when NOT to use it, is the skill that will land you your next job. Or would you in 2030 expect to hire software devs that never touched AI?

I'm probably a worse programmer than I was before I started using frontier AI models, in the sense that I probably have a harder time reading, writing, and debugging code. And I doubt that my knowledge of the AI models themselves will have lasting practical value. But I know substantially more about UEFI, PCIDs, seL4, WebAssembly, GLSL, Service Workers, CORS, server-sent events, CSS, content-security policies, memory-hard PBKDFs, Android, numerical integration, Verilog, V8 security, Linux process namespaces, hypervisors with VT- x, multitouch user interface design, radio communications theory, power electronics, physical-layer communications protocols, NTSC video signals, TLA+, bounded model checking, generative testing, theorem provers, FPGAs, Linux system call overhead, Unix mailbox formats, physical modeling synthesis, damped resonance, KaTeX, geology, dishwashing detergent, microbiology, Cyclone, thermodynamics, X-Windows, localStorage, AVX, and IndexedDB, for example.

I think this comment does a good job of explaining how the breadth of what software engineers do is going to change even more. And again, we are still early. Find a domain to work in!

I don't know, this might be year #81 of the 82 years in which humans create software. Or it might be year #81 of 82 billion years. Anybody who tells you they know what's going to happen is full of shit.

I do know it's year 1 of n of me being crazy productive. I was already a good developer. Turns out I'm a damn good business analyst/bot farmer/and developer.

[delayed]