|
|
|
|
|
by davnicwil
41 days ago
|
|
One way I like to think about is that often abstraction is an automation for a task that doesn't need automating. You hardly ever change the thing and if you do, changing it in two or three places 'manually' is really not a big deal. Now changing something fairly often, that affects logic in 50+ places? Then it makes sense to automate with an abstraction so it all flows through the same lines of code. I know I've personally spent way more time over the years debugging bad abstractions than changing things in a few places. |
|