The hardest programming habit for me to kill has been putting variable declarations at the top of a function definition instead of in-line where they are first used. I learned to group variable declarations "out of the way" at the top of the function while learning to program C back in school. Thirty-some-odd years later and I still want to move declarations up to the top, but it's worse for readability, not better. Locality of pertinent facts is a good thing.
=> More informations about this toot | More toots from binaryphile@fosstodon.org
@binaryphile i'm the same way, the only thing that has changed my behavior has been the use of more closures. for some reason my ancient C brain feels safe as long as the variables are near an open curly brace XD
=> More informations about this toot | More toots from elmiko@fosstodon.org
@elmiko My brain has been fairly plastic when it comes to reshaping my programming patterns, probably because I'm constantly working on it, but this is one pattern that has been remarkably recalcitrant for some reason.
=> More informations about this toot | More toots from binaryphile@fosstodon.org
@binaryphile preaching to the choir, i feel so similar. i even do it in python lol.
=> More informations about this toot | More toots from elmiko@fosstodon.org
@binaryphile
Same.
Unlearned is often harder that learning.
=> More informations about this toot | More toots from brouhaha@mastodon.social This content has been proxied by September (ba2dc).Proxy Information
text/gemini