3 ms·
Understood, but I would caution that even an inexperienced, inefficient programmer should still understand what their code does and why it works. The best way t
by RyanMcGreal 15y ago
Understood, but I would caution that even an inexperienced, inefficient programmer should still understand what their code does and why it works. The best way the more experienced can exercise patience is by giving inexperienced programmers enough time to figure it out rather than pressuring them to flip random switches frantically.
- tsumnia 15y agoI think that just touches on documentation, extensive commenting, and generally writing straightforward code. I didn't really know the importance of this until I had to step-by-step rewrite my thesis after it fell apart completely. Now, I make sure to document at the least a small explanation of what my lines of code mean and the end result, no matter how simple.
- onemoreact 15y agoWith a little time, inexperienced and inefficent programmers can understand often understand the crappy code they wrote just fine. What they can't do is avoid writting it in the first place. For most of them if you say great this works now make it better they will have zero understanding in what direction they should try and improve things.
- throwawayday 15y agoit's called experience for a reason - the coder has to try (and fail) until they learn enough to code good, efficient, clear code