3 ms·

This does not sound very radical at all. Software engineering will no doubt be transformed within 10 years and there’s plenty of uncertainty around what our fut

This does not sound very radical at all. Software engineering will no doubt be transformed within 10 years and there’s plenty of uncertainty around what our future employment needs will be for people who primarily code. I feel vary similar about going into any kind of commercial art, writing, game development or SFX design.

PodgieTar 3y ago
It does sound radical, at least to me. We've been abstracting away for years. Programming languages are an abstraction away from machine code. Libraries abstract away things like common sort, search algorithms. Despite that, I still think it is advantageous to have knowledge of those concepts. I'm not saying you should program in assembly, but you should have a broad understanding of the difference between compiled and JIT languages. You shouldn't necessarily need to know the implementations of Linked Lists or Hash Maps, but understanding when they should be used is important. Reading code, even if writing it becomes more obsolete over time, will still be an important skill, because being able to compartmentalise and understand code will still be important for debugging. There are a lot of skills that you learn when you learn software engineering, some of them are foundational skills that, even though they'll be transformed, will still be essential.