I know these kinda questions get asked a lot these days, but hear me out.
I’m a junior-going-on-medior software engineer, graduated last year and have been (more or less) teaching programming for four years.
In my search to find meaning in life, I stumbled into programming and found that there was a lot to learn. I loved it. That’s why I eventually chose to switch careers once I musterred enoigh resources to do so. I chose this job because I like learning and I want to keep learning for the rest of my life. I love the way how learning is an integral part of the programming community and how everyone encourages and stimulates it.
AI has changed the job of an swe, that much I understand. That is not a deal breaker for me, as long as there is still a lot of meaningful, worthwhile, marketable things to learn. I am using AI to learn things faster now, but there is an easy pittfall to actually learn nothing from AI. Some say we don’t have to learn anything anymore, I don’t think that is true, but then what is true?
How is AI affecting the learning aspect of this job? Is learning still an important part of the job? Is there still enough worthwhile things to learn? Is it still valuable to learn more?


Using AI doesn’t mean you shouldn’t learn how the systems you are working on or building work, or what tech stack choices are good for what purposes, or what’s happening under the hood in the systems you’re working on. In fact, learning these things is critical for being able to drive and review work to correct outcomes and efficient operation.
Whilst it might be useful to be aware of certain design patterns, coding concepts, and other low level details of how languages work it’s unlikely you’ll be applying these concepts yourself - but you must still be able to recognise and understand them. They don’t go away in an AI world.
Understanding how things work and when to apply what methods and technologies is still as critical as ever, and is the difference between an engineer using AI on the job, vs an executive vibe coding some shit that doesn’t operate scalably, or work on other computers, or can even be hosted safely.
If you can’t explain what’s happening inside the computer when you run any random line of code, start there. You should know when you’re going to disk, or memory, or network, what the costs are, what happens when async code awaits, when you spawn threads, spawn processes, put sync code in async code, put async code in sync code, what the TCP stack is doing when you send data, what the UDP stack does differently when you send data, why you don’t put slow operations in the main thread, what healthy caching looks like, what happens when unexpected things go wrong and how to handle those situations, etc