It's a Trap! How Abstractions Have Failed Us.

What does Kubernetes, React, a compiler, or even the OS Kernel all have in common?

They're all a form of abstraction! You might be asking yourself is that a bad thing? If so, why?

Our systems are too complex and we keep building layers of abstractions in a vain effort to simplify these same systems. We start out with a simple problem and somehow end up with a solution that requires more investment and maintenance than the original problem itself.

Why do we do this? You can argue that our industry incentivizes this because you can use it to get that new job, get a raise, or gain that 31337 clout. You can argue that we do this to ourselves by conflating simplicity with lack of intelligence (or experience). Either way, we're paying a cost for all this abstraction:

• The abstraction has taken on a life of its own and takes you with it
• We lose proficiency with the foundation
• We lose sight of the original problem
• We don't forget about the people this is supposed to help
• We keep using and modifying the abstraction even if it is no longer appropriate

Not all abstractions are bad, we just don don't know where to stop. So what do we do about it? We can't reasonably expect never to use an abstraction again. In my session, I'd like to share my experience with conquering the never-ending chase down the abstraction rabbit hole and to hear your stories and solutions too.