3 ms·
> A naive look at this and my head is screaming that this file is way too big, has way too many branches and nested if statements. A naive look at this and my
by bb88 8y ago
> A naive look at this and my head is screaming that this file is way too big, has way too many branches and nested if statements. A naive look at this and my head is screaming that this file is way too big, has way too many branches and nested if statements, has a lot of "pointless comments" that just describe what the line or few lines around it is doing, and has a lot of "logic" in the comments which could quickly become outdated or wrong compared to the actual code.
I actually understood it immediately when I read it. There's something to be said when you have a decent roadmap for debugging critical code segments. It's not just software maintenance here, it's for the "holy crap something went wrong and we can't understand how we got here!" moments.
- erikpukinskis 8y agoThis is why I prefer older JavaScript to the more recent stuff, with transpiration pipelines and AI-like optimizing compilers that gnaw on giant state trees. That stuff is lovely and terse when it works. And when it doesn’t you are at a total loss. The beauty of imperative code is there’s a beginning and an end, and at every step you can easily see what follows and without too much work what came before.