Every time I see a team celebrating their new "shared module," I remember this lesson.
Reuse is a dangerous form of coupling.
They found the same logic in two places and did what good engineers do: put it in one place and called it a win. Clean, responsible, textbook.
Six months later, someone needs to change it.
Suddenly, a small update for one team's requirements breaks three services, blocks two releases, and triggers an emergency meeting between people who've never talked to each other before.
This is the cost nobody preaches about.
DRY is one of those principles that feels unquestionably right until you apply it across team boundaries. The moment you share a module between domains, you're not just sharing code. You're creating a dependency that nobody owns and everyone resents.
Before you reuse, ask:
Will this change often?
Does it belong to one domain?
Are the consumers truly aligned in purpose?
Will one team’s change surprise another team?
If the answer to any of these is "I'm not sure," stop. Duplicate it.
I know how that sounds. It feels lazy. It feels like the thing a junior developer does before they know better. But here's what nobody wants to say out loud: two independent implementations you control are almost always cheaper than one shared one serving masters with different goals.
Duplication is a local problem. Coupling is an organizational problem.
One of them you can fix in an afternoon. The other requires a meeting with five teams and someone's manager.
Reuse isn't free. Treat it like the trade-off it is.
AI is changing how we contribute to open source.
A detailed issue with clear context and acceptance criteria might now be more helpful than a PR. The maintainer can use their own AI tools with full project context to implement it well.
The value shifts from writing code to describing the problem clearly. This is what Spec-Driven Development is about.
I remain locked in perpetual whiplash, oscillating between two theses: AI is a diabolically efficient timesink, or it is the most useful invention since sliced bread. The oscillation continues.
I am writing this while my local AI server plays an extended game of digital hide-and-seek with a bug that has evaded me for ages. So far it has suggested perfectly reasonable fixes that prove utterly useless, like chocolate teapots in a blizzard.
FSD V14 is incredibly hyper-aware. The moment the blinker comes on, it recognizes this isn’t just a normal lane change, but a risky move to cut across for the exit. It starts braking in just 0.25 seconds. No human can match that.
@CertumIter Le prix de la location est relativement bon marché si on tient compte du prix de l'immobilier. Le probl��me fondamental est que la demande pour l'immobilier dépasse l'offre de manière chronique.
@nantermod J’espère que mon appréciation du sujet est erronée. Mais à mon avis, c’est l’une des propositions les plus absurdes jamais sorties du Parlement suisse.
@CertumIter@WesRoth@ylecun To what extent is Yann LeCun aware of the various techniques recently introduced by Grok or Gemini? The state of the art does not stand still.