In the final Bikeshed column, I, Poul-Henning Kamp, reflect on the future of FOSS and the growing pains of the industry. Two hot envelopes dominate: LLM‑assisted code reviews and age verification. Though headlines swirl, my experience suggests the first wave of bugs is already on the table, echoing patterns seen with Clang’s static analysis.

The pattern is familiar: Day 1–2, a tool appears promising; Day 3–5, bugs surface; Week 2, the cycle repeats. This cycle, first noticed with Zilog Zeus in 1984, now surfaces with LLMs. The cost lies in upfront training, unify the resulting model weights fit on pocket‑sized storage—much like a blockbuster film that can be sold repeatedly.

Age verification, meanwhile, threatens the very fabric of FOSS. Encryption, once a shield, now forces a shift toward cryptographically attested software. The result: a more accountable ecosystem where the source may be open, but the platform is signed and tamper‑proof.

I warn that the tech bros’ push for privacy has backfired, shrinking anonymity and paving the way for mandatory checks. As a parent, I welcome stronger safeguards, but I caution that FOSS must adapt by embracing signed builds and platform integrity. The future will hinge on whether the industry can balance openness with accountability without surrendering the very freedom that fuels innovation.