We have used too many levels of abstractions
One cause I&#x27;ve seen of this is the &quot;college is not needed to be a coder&quot; trend from the past few years (decade?). it is true that most of my skills were acquired after college, but there is some sort of global system understanding that you get from college (in my case computer+software+network engineering) where you can quickly narrow down potential sources of a problem, all the way down to say, the TCP&#x2F;IP stack, CPU architecture, memory management, how some code might be optimized incorrectly by the compiler. It also helps a lot in asking the right questions. If all you know is [latest framework&#x2F;language&#x2F;tool], there is a whole world around this that can bite you when circumstances stop being perfect.
One superpower is looking at a marketing page for a tool and knowing within seconds what it can&#x27;t do and whether it would be a good fit for your use case, just by what is claimed on the page.<p>Regarding abstractions: I&#x27;ve sort of always ran away from languages that encourage it a lot. Java was one of them, where the entire OOP trend just fell flat to me even in college (I understood the benefits, but meh). The concept of dependency injection is another one, I think it was introduced in Javascript? Idk, I use it if the framework forces me to, but IMHO, it only makes sense when I&#x27;m the one building it. Define constructors that take interfaces and instantiate them explicitly with whatever implementations you want (ie. mocks vs real, etc). So that you understand everything that is happening.<p>My Biggest fear with frameworks (especially JS) is they are abstracted to such a level that I can&#x27;t hope to fix an issue in a reasonable amount of time without begging for help in forums or github bc I don&#x27;t understand even the concepts. What  are effects? How does react work? How does Angular work? etc.