2 ms·

You're right most engineers are missing core concepts. You're wrong that it was ever different than it is today. I suspect your observation results from your i

You're right most engineers are missing core concepts. You're wrong that it was ever different than it is today. I suspect your observation results from your improvement over time. Plus, your relative skill level monotonically increases as others retire and juniors replace them - even if you stay stagnant. There's other causes too; - Major tech fads (remind me - is OOP in fashion or not right now?) - New topical emphases for industry (is is more important to take that second data structures class, or that first LLM class?) - A changing definition of who is an engineer (should business analysts by deploying pipelines in the data warehouse?) All this to say: there's probably more people with a fantastic understanding of software engineering today than there ever has been. And the likelihood of working with one of them might still be lower than it ever has been.

rawgabbit 3y ago
Replying to - Major tech fads (remind me - is OOP in fashion or not right now?) It depends on the definition of OOP which we can never agree on. This site says Alan Kay's definition is: OOP to me means only messaging, local retention and protection and hiding of state-process, and extreme LateBinding of all things. https://wiki.c2.com/?AlanKaysDefinitionOfObjectOriented https://wiki.c2.com/?AlanKaysDefinitionOfObjectOriented My personal feeling is that people are tired of talking about OOP. It is as useful as arguing what Agile is. I find it more interesting to talk about the motivations behind new computer languages, people are inventing. e.g., Rust claims the main purpose of using Rust is enhanced safety, speed, and concurrency, or the ability to run multiple computations parallelly. e.g., Kotlin claims it makes coding concise with less boilerplate.