It’s this way for anyone who’s good or bad at anything.
If you’re not good, you’ll be confused and clumsily try to get the results you want. If you’re good, you actually understand what you’re doing and make deliberate strokes.
If you’re not good, you’ll be confused and clumsily try to get the results you want. If you’re good, you actually understand what you’re doing and make deliberate strokes.
In contrast, tell a crank to write code, and you'll end up with the programming equivalent of Finnegan's Wake (or, if you're unlucky, Timecube). Execution paths meander and ultimately lead nowhere; comments which are not just wrong, but bear no relation to any nearby code; often, remarks that the compiler is wrong and only the crank is aware.
Crank code can be amusing to read, but I can't imagine dealing with it in a professional environment.