Learn how reasonable people think about the best tools for which use-cases, e.g. Rust instead of Python
4. My Observations
The hardest part of building software is not coding, it's requirements
Requirements are usually specified by business owners who have no idea the complexity involved with every extra word included on the spec sheet
Trade-offs need to be made after considering tech stacks, cost, manpower, security, timeline, business risks, policy blockers
But none of these can be done with poor understanding of foundational technologies that make the web tick
If you're good enough, you can use any language/framework/libraries to build crazy stuff, but doing so can be inefficient and low ROI
Almost all architectures/tools/frameworks are good at some stuff and lacking in others - the key is to make informed choices for the problem we're solving, not be dogmatic
Business processes, service processes, policies can block technical and lead to unnecessary poor outcomes