[leoharsha2]

These are the other things that a developer should know -

1- Focus on the problem and not the tools ceremony around it. 2-Don't follow the herd and the hype. When given a problem, keep drilling the problem until it is absolutely clear to you and then only work on solution.

Meta-habit: learn to adopt different habits for different situations. With that in mind, some techniques I've found useful for various situations:

When developing for yourself or a small team, let problems accumulate and fix them all at once (or throw out the code base and start anew). When developing for a large team, never let problems accumulate; the code base should always be in a state where a new developer could look at it and say "I know what this does and how to change it." This is a consequence of the reader:writer ratio - startup code is written a lot more than it is read and so readability matters little, but mature code is read much more than it is written. (Switching to the latter culture when you need to develop like the former to get users & funding & stay alive is left as an exercise for the reader.)

[HeroOfAges]

2-Don't follow the herd and the hype. When given a problem, keep drilling the problem until it is absolutely clear to you and then only work on solution

This is one of the most frustrating things I've had to deal with when developing with a team. No one wants to take the time to think about a problem before working on a solution. Almost always, the people I work with would rather spend weeks coding than spend a few hours thinking about the problem, just so they can present a solution "first". It drives me crazy!