sparkle bat: The ways I continually streamline platform abstraction stuff to be useful services that get the hell out of the way of business logic as efficiently as possible

Beware the beautiful abstractions that subtly replace the requirements of the software with their own preservation

The ways I continually streamline platform abstraction stuff to be useful services that get the hell out of the way of business logic as efficiently as possible

(mostly I land on abstractions as contextual awareness and conflict resolution machines)

Abstractions are great - including really beautiful ones - but what was on my mind yesterday is how appealing they can be to software developers, and how they can become the priority over the task they're trying to solve

I imagine there’s a kind of time/effort box a dev has to keep in mind when picking one to use?

In my work I try to be the help devs need as opposed to help they don’t need lol

Post