Sometimes another layer of abstraction is not the answer. And sometimes the path that led you to believe you needed one, actually should tell you that you’ve built so many layers on the wrong foundation that it is time to burn it all down and start over.

Jan 26, 2024 · 2:39 AM UTC

8
8
1
68
Replying to @JamesWard
Which foundation are you working on now?
1
I'm not really sure. Too many layers of abstraction.
2
Replying to @JamesWard
One abstraction’s foundation is another foundation’s abstraction.
3
Replying to @JamesWard
The good layers of abstraction allow to understand and better the underlying technology so to be able to modify the behavior swiftly. The bad abstractions are the ones that add accidental complexity promising w/o success a quicker understanding or expansibility. My 2 cents
2
Replying to @JamesWard
James, the CNCF would like to have a word with you. That word is “STOP”.
2
Replying to @JamesWard
When you create a "white cat named bill" abstraction, what can go wrong? Or..."foo doing goo"-likes too. Only flowers can grow out of sh*t, while code just smell worse
Replying to @JamesWard
If you think about it, "level of abstraction" is an awkward term. It is not natural to have layers of something abstract - unrealistic. We can have more separations, yes but not of abstractions.
Load more