I partially disagree with what has been said here. Fundamental engineering skills are things you learn at school. Theory over reality, by default, we're all goo

I partially disagree with what has been said here. Fundamental engineering skills are things you learn at school. Theory over reality, by default, we're all good engineers with a CS degree right? In my opinion you have to implement that theory in real life in order to complete your courses, which is when stacks come into the picture. Learning a new stack is extremely important for an engineer because it exposes you to a lot of new problems. Things you've never heard of, unless you already got your hands dirty. I'm talking about reading poor API documentations doing reverse engineering work, understanding how to implement a concept and the large gaps between paper and code, how to pick up the right tools for your needs which will save you time and money moving forward, how to integrate, etc. Integration is about %70 of our work today. If you haven't used at least 2 different stacks in your life, you ain't know about integration problems. So, yes, engineering is a lot more than a set of concepts. I would value someone who jumped into a bunch of different stacks rather than a google-like engineer who doesn't even know how to right HTML (which is a real joke between ex-googlers, we say we didn't even know how to write an HTML page when we left google).