All good and straight-forward points. Once you internalize these, you are on the way to being a "code craftsman" - someone who knows their tools well yet is hum

All good and straight-forward points. Once you internalize these, you are on the way to being a "code craftsman" - someone who knows their tools well yet is humble enough to ask for help & make himself/herself uncomfortable again and again in the quest of more understanding. Personally, the number one technique that helped me grow was to always ask "How & Why is this feature/framework/Technology important to the end goals of the business/product?" As you start being entrusted with more complex systems the amount of "religious" arguments begin to multiply (Java is slow, Ruby is cool, Python is old, Mongo is the hotness, Postgre is for old farts,...) At this point focus on the Business needs ..What is absolutely essential?