3 ms·
"Going dark" might be more acceptable to senior programmer types who already have a strong grasp of software development concept, accepted idioms, and basic cod
by noonespecial 18y ago
"Going dark" might be more acceptable to senior programmer types who already have a strong grasp of software development concept, accepted idioms, and basic coding style.
They seasoned expert is like likely to return after his dark period with something consistent, clearly written and mostly bug free. (Especially the troublesome design flaw bugs).
The junior programmer who goes dark mostly out of fear of criticism is likely to return with something that has no consistent style, mixed up idioms and likely fundamental system-wide design flaws that require rewrite.
The important difference here is the reason these two different classes of developers choose these long dark periods. The first developer wants to be free of politics, interruptions and nitpicking while he builds what he knows how to build. The second is afraid of criticism as he stumbles through unfamiliar territory hoping that if he can get it to "just work" it will hide his ignorance.
Denying the first his time might cost you something truly great that you otherwise won't be able to get. Allowing the second cheats the junior of a valuable learning experience and simply allows him to continue in bad practices, gaining "experience" without any real increase in know-how, thus generating the strange coder we;ve all met with "20 years of experience in blub" who writes unusable code.