shiny new thing syndrome:
people love coining new words for old problems. they get excited by "new ideas" and rush to build new frameworks, new concepts, new abstractions β when what they actually need already exists. it just needs to be more robust, more extensible, better fitted with the rest of the system.
shiny new thing syndrome adds unnecessary complexity. every new thing tips the balance of the whole. if you keep adding, and adding, and suddenly you have a tower of abstractions that's too complicated to reason about. it becomes unstable. fragile.
the real art isn't in creating new things β it's in seeing what's already there. lose the blinders. look at the whole, not just the part you're excited about. don't over-optimize every single piece. sometimes the best move is to use what exists and make it better, not reinvent it with a shinier name.
most things aren't new. they're just repackaged. the concepts underneath are the same β databases, views, functions, state. if you can see past the surface, you realize we're all just rearranging the same fundamental pieces.
the question isn't "what new thing can i build?" it's "what already works that i can make truly better?"