“Je n’ai fait celle-ci plus longue que parce que je n’ai pas eu le loisir de la faire plus courte.” -Blaise Pascal Complexity is not planned, it is created tho

“Je n’ai fait celle-ci plus longue que parce que je n’ai pas eu le loisir de la faire plus courte.” -Blaise Pascal Complexity is not planned, it is created though expediency. Devs use that database because they’ve done it before, they know how to use it, and they have a bunch of code segments to reuse. It gets them one step closer to solving the problem. An elegant solution, presumably some form of binary serialization, would require a learning how, and maybe rethinking objects to strip out cruft and make serializable state, and then coming up with an efficient access pattern. All these things are nice elegant composable tools available somewhere, but not at the top of mind like MySQL, which you’ve been using since your first programming course. I’ve been doing a lot of work with C++20 templates recently. The simplicity and reasonability benefits can be enormous, but the time it takes to learn, design, and craft them is completely oblivious to the person reviewing the code, if it ever gets reviewed at all. In a corporate setting, the only thing anybody sees is lines of code. Remote work has strengthened this anti-pattern. Nobody sees the time or diligence with which you craft solutions. Elegance looks like nothing.