001-Core Programming: Why Bother to Improve Your Coding? I am on probably my fourth or fifth version (hopefully a final version) of my software. — Steven
There is an old saying... "Being a programmer means
never having to say you are finished."
I don't get away with zero documentation/notation but I am pretty much to minimum documentation/notation. I had to abandon hundreds of hours of code in order to write better code. — Steven
I feel your pain.
I had to abandon over 10,000 hours worth of working code from HSH!
(That's 2/3s of all the coding I did in of 20 years on HSH!)
I've built a strict rule:
"All new code will fit my personal
10-x Coding Standards."
I am sure you know how difficult this is - to take the CODING HIGH ROAD for everything new.
Like, I was writing a simple set of list-up/down buttons.
Imagine, you have an alpha list but you want it sorted in a LOGICAL ORDER way.
Further, you don't want the user to have to ever type in a logical order number.
In HSH, I actually used numbers, but I vowed to do better code in the Studio and going forward.
So, I bit the bullet and spent about 15 hours writing a set of functions to manage this, instead of maybe 1 hour to get it working the old way.
(If you want to know how it works, I'd be happy to show you.)
But there was a payoff.
I've now used it in about 10 different browses, and have begun to reap the returns, because it now takes about 15 minutes to facilitate adding those buttons and making them functional in any browse!
Not EVEN yet, but getting there.