What the UK Tobacco Ban Teaches Builders About Norms

The UK generational tobacco ban is the kind of policy that looks doomed on paper: a law that quietly makes it illegal to ever sell cigarettes to anyone born after a certain year. Enforcement will be patchy. Black markets exist. And yet the writer of a recent MIT Technology Review piece says he supports it anyway, and his reason is more interesting than the law itself.

His evidence is his own two daughters. They learn AI at school, do internet homework every week, and are already repulsed by the idea of smoking. The ban isn't creating that attitude. It's ratifying a shift that already happened in their heads.

🚬 The real bet is on norms, not police

The stated worry about the ban is enforcement. A shopkeeper checking whether a 30-year-old was born before or after a cutoff date is not a system that scales cleanly. Critics are right that the mechanism is clumsy.

But that framing misses the point. A rule you can barely enforce can still work if the behaviour it targets is already becoming socially dead.

Key takeaway: Enforcement stops the people who still want to do the thing. Norms stop them from wanting to in the first place. The second one is far cheaper and far more durable.

The author's kids aren't avoiding cigarettes because a law scares them. They avoid them because smoking now reads, to a seven-year-old, as gross and old-fashioned. That is the actual win. The law is a backstop for the small minority the norm doesn't reach.

🧠 Why "it might not work" isn't a reason to skip it

There's a familiar engineering instinct here: if a control has known gaps, ship nothing until you have a perfect one. That instinct is usually wrong, and this policy is a good illustration of why.

Consider how the two levers compare:

A ban with holes in it still moves the norm line. It signals what a society has decided is no longer normal, and that signal does most of the heavy lifting for free. "Might not work perfectly" and "worth doing" are not in conflict.

🛠️ How this maps to what you build

If you build software, run a small team, or ship anything people interact with, you are constantly choosing between the enforcement lever and the norm lever. Most people over-invest in the first.

A few translations that hold up:

• Defaults beat rules. A secure default (2FA on, telemetry off, safe git branch protection) changes behaviour for everyone silently. A policy document nobody reads changes it for no one.
• Friction is a norm, not a wall. You rarely need to make bad behaviour impossible. Making it slightly annoying — a confirmation step, a required review — moves the vast majority.
• What the newcomers see as normal wins. The junior who joins your repo copies whatever the code already does. If tests and small commits are the visible norm, that becomes their default without a single lecture.
• You can't audit your way to culture. You can require a linter. You can't require people to care. The linter's job is to make caring the path of least resistance.

The generational ban is basically a default: deny for a whole birth cohort. You set the rule once, and the culture enforces most of it so you don't have to.

The same logic sits behind why setting good defaults early is worth more than any amount of after-the-fact policing.

🌐 The Sri Lanka angle

This is not an abstract UK story. Anyone who has watched a norm flip in Sri Lanka within one generation already knows the pattern.

Seatbelts in the front seat went from optional to automatic for a lot of people in under two decades, helped by a law that was never enforced everywhere at once. Not wearing a helmet on a motorbike went from common to conspicuous. Digital payments moved from "who would trust that" to routine for a young office worker in Colombo or Galle, faster than any regulator planned.

In each case the rule and the culture pushed together. The rule alone would have been ignored. The culture alone would have taken a generation longer.

For a young builder here, the practical read is this:

1. Pick the norm you want to be normal in five years. Clean code, honest pricing, accessible interfaces, whatever it is.
2. Encode it as a default, not a rule you have to remember to enforce.
3. Let the newcomers absorb it as "just how we do things," which is where it becomes permanent.

💡 What this means for you

You don't need airtight enforcement to change behaviour. You need to move the line of what counts as normal, and then let time and defaults do the boring work.

The UK tobacco ban may leak. The author admits as much. He supports it anyway because his daughters have already made the real decision, and the law is just the state catching up to where the culture went.

If you're shipping a product, growing a team, or trying to get a habit to stick — in code or in life — copy the structure, not the cigarettes:

• Set the default in your favour.
• Accept that it won't catch everyone.
• Trust that the norm, once it tips, does more than any rulebook you could write.

That's a lesson worth stealing, whether you're regulating tobacco or just trying to get people to write tests. When you want more small, opinionated defaults that quietly do the right thing, the free tools on this site are built on exactly that idea.