What generics and open source have in common

The first time I studied generic medicines properly, I recognised something. Generic drugs and open source software are the same argument, made in two industries: knowledge already paid for should compound for everyone; access should be wide; and trust should come from verification, not branding.

The shared structure

The original proves the recipe; the copies prove the system. A brand drug proves the molecule works. Generics prove the manufacturing process can reproduce it — bioequivalence, not novelty. Open source: the original project proves the idea; forks and reimplementations prove the ecosystem can sustain it. Both systems advance by verification, not invention alone.

Access changes outcomes. Generic competition collapses prices and widens access — the public-health argument is settled. Open source does the same for software: a student in Nsukka runs the same web server as a billion-dollar company. Access to infrastructure flattens opportunity, in both fields.

Trust must be re-earned per source. A generic must prove its factory meets standard; not every copy is equal. Open source consumers must check their supply chain; not every package is safe. Brand trust is insufficient in both worlds — verification is the actual currency.

What each field could teach the other

Pharmacy has mature quality systems — GMP, pharmacovigilance, batch tracing — that open source supply chains are still inventing. Open source has fluid, global collaboration that pharma's silos could envy. Both trades are arguing the same thesis from opposite ends: openness, with rigour, wins. I happen to be studying both arguments at once.