[gddr]

You basically just explained good software engineering. Code that does one, well-defined, necessary thing and does it well.

If you want to "do a thing", a DoThing() function is the optimal way to represent it. You can't get any more abstract than that, and you don't need to.

Somehow a lot of (badly explained) ideas of "design patterns" and "abstraction" have rotted people's brains into thinking you're supposed to add a whole bunch of extra layers everywhere.

[Aeolun]

Depends on how many DoThing’s you have in your code and on how many other DoThing’s they depend.