_I don’t care if you’re junior or senior: when writing code at this standard of quality, caution and rigor are always part of the process_ There are (at least)

_I don’t care if you’re junior or senior: when writing code at this standard of quality, caution and rigor are always part of the process_ There are (at least) three stages for a program: make it work, make it good, make it fast. Most programmers I know (aka juniors) are happy to get the first stage done, for a value of done (it worked on my machine, when I tested it with this particular sequence). After many, many years of programming (aka senior), I'm proud to say that I usually take care of the second stage, and sometimes even the third. The whole point of the junior / senior distinction is that seniors have been burned more times by some things so they insist on processes like always having source control, at least trying to have automated tests and so on - processes that a lot of juniors find irrelevant to getting things to work in the first place.