3 ms·
> and it's the kind of readability refactor that you'd often want to do anyway even if the code wasn't being shared. Couldn't disagree more tbh. Some of the wo
by BigJono 4y ago
> and it's the kind of readability refactor that you'd often want to do anyway even if the code wasn't being shared.
Couldn't disagree more tbh. Some of the worst code I've ever had to work with has been over abstracted "recipe" code where I'm trying to descern complex processes based off two word descriptions of them in function names.
Doing this too much is a great way to turn a readable 100 line algorithm into a 250 line clusterfuck spread across 16 files.
- biorach 4y ago> Doing this too much ok, so you're talking about overdoing it. It's still a good approach when done right.
- BigJono 4y agoNot really, unless "done right" is for like a 2000 line function or something. If code is running once in order, there's no reason to break it up into functions and take it out of execution order. That's just stupid.