From 30+ years of dev work: > - There is no substitute for doing. Less tutorials, more coding. I'd rephrase that as "just write something!" Many times I find

From 30+ years of dev work: > - There is no substitute for doing. Less tutorials, more coding. I'd rephrase that as "just write something!" Many times I find myself being the classic example of 'perfect is the enemy of good' - I'll think about the perfect solution, rather than write something *now*, that works, and refactor towards perfect. TDD and all that. Other things: - Beware the beta and the boss. If it works, it will invariably get shipped if your manager sees it. Many managers cannot put a value on the future cost of maintaining something that's barely good enough. - Classic Confucius: "I hear and I forget. I see and I remember. I do and I understand." If you're interested enough to read about some tech/language/framework, write something (again!). - Learn at least one other language and ecosystem in addition to your main one. Even if it is syntactically similar (C++, Java, C#, for example).