How to Keep Bad Abstractions From Handcuffing Your Code
What happens when you have a bad abstraction? You have to dig out the API reference every time to understand what that method that clearly should have been named leaderboard
is actually called. And whenever you touch the code, something breaks, and you blow the rest of your day trying to debug it (because you tweaked position
, but didn’t update score
at the same time). So how do you build good abstractions, while staying far away from the bad?
Post a comment