Joel Spolsky

And...

I think Joule, who invented this, I forgot his last name, he invented this concept called leaked abstraction, right? Where the abstraction you just created, it just leaked back to you in form of CPU 100% usage in terms of complexity, in terms of performance.

You're going to feel it later, right? And that's the challenge we're having.

And sometimes you're going to use it.

Right.

I think it was, was it Jeff Atwood talked about performance as a feature? Joel Spolsky is one of our founders, had a performance as a feature sort of thing.

And it's like, well, you don't have to focus on that feature from the outset, right?

Absolutely.

It elegantly hides the complex, mathematical, and often brutal reality of relational databases behind beautiful, intuitive Pythonic objects.

But brings to mind the law of leaky abstractions, coined by Joel Spolsky.

Oh, that's a great reference.

The law states that all non-trivial abstractions to some degree are leaky, meaning eventually the abstraction breaks down and you have to understand the underlying complex system to actually fix it.