The New York Knicks reached the NBA Finals after letting go of their superstars, a similar turn to what Paris Saint-Germain is attempting. After years of disappointments, the team rebuilt from the ground up to compete for the championship. For New York fans, this shows that prioritizing collective work over big names can be more effective than accumulating ego in the locker room.
The technical lesson: optimize the system before the hardware 🛠️
In software development, this phenomenon is replicated when a team discards heavy frameworks or trendy libraries to return to modular, lightweight structures. Just as the Knicks let go of their stars to enhance specific roles, in programming, bloated dependencies are removed in favor of clean, scalable code. The result is not more raw power, but better cohesion: processes run with less friction and maintenance is simplified. Sometimes, deleting and rewriting from scratch is more cost-effective than patching what no longer works.
Goodbye to the stars, hello to the anonymous workhorses 🏀
The curious thing is that while the Knicks succeed without media spotlights, in the NBA there are still teams that sign three stars only to see them fight over the ball. It's like installing a next-generation processor on a rusty motherboard: a lot of noise, few baskets. In the end, the lesson is simple: better to have five guys who pass the ball than a diva who demands 90% of the shots. Even the bench appreciates it.