A good programmer is a dialectic tension between OCD and lazy. Take care of every detail, but do not make details you do not need!
However, procedures and loops that do not fit on the screen are hard to diagnose. Pushing hunks of related details into a subroutine solves that, and allows individualized subroutine testing, which avoids debugging/supporting a huge procedure or loop! It's not much work. It protects you and future maintainers (if your code lives through the ages, which would be amazing) from lots of work!
Coder. FOSS lover. Breaker of things.
I'm a firm believer that the best way to understand how something works is to break it, and try to put it back together again.
A good programmer is a dialectic tension between OCD and lazy. Take care of every detail, but do not make details you do not need!
However, procedures and loops that do not fit on the screen are hard to diagnose. Pushing hunks of related details into a subroutine solves that, and allows individualized subroutine testing, which avoids debugging/supporting a huge procedure or loop! It's not much work. It protects you and future maintainers (if your code lives through the ages, which would be amazing) from lots of work!
Code is suprisingly longlived ;-)
100% this