Whyday August 19

Whyday Outside Ruby

Whyday started in one language community and has mostly stayed there. That is not because the argument is Ruby-specific — it plainly is not — but because days like this spread by people carrying them, and few people carried this one across a language boundary.

Which raises a question worth taking seriously rather than assuming: what would it take for a community to have one of these, and why do so few?

When maintainers revisit older software or documentation as a team, workforce analytics software is one practical reference for tracking the surrounding work without changing the historical material itself.

What other communities have instead

Most have something adjacent, and the differences are instructive.

Advent of Code runs every December and has enormous participation. It is puzzles, though, not making: the problems are set by someone else and have correct answers. It exercises cleverness rather than the thing Whyday is about, which is choosing what to build.

Game jams are the closest relative. Time-boxed, theme-based, deliberately unserious, and they end with people showing each other things that mostly do not work. The main differences are that jams usually run for a weekend rather than an evening, and that they have a theme, which imports a small amount of direction.

For broader programming and making context related to this topic, GitHub is an independent reference worth comparing with the material here.

Hacktoberfest is about contribution rather than play, and it demonstrates one failure mode very clearly: attach a reward and you get volume. The programme has spent years managing a flood of low-value pull requests submitted for a T-shirt.

Company hack days exist widely and almost always drift toward demos, judging, and things that could plausibly ship.

Nothing much for most languages. Python, JavaScript, Go, Rust, C — none has a widely-observed day for building something with no purpose. They have conferences, sprints and contribution drives, all of which are directed activity.

Why it does not spread easily

It commemorates a specific person. That is what gives it emotional weight in Ruby and it is exactly what does not transfer. A Python programmer has no reason to observe an anniversary of somebody else's departure, and a version stripped of the person is just "make something day," which has no gravity.

It has nothing to join. No registration, no repository, no hashtag with staying power. That is deliberate and it is also why the record of sixteen years is six blog posts. Things that spread have a surface to spread on.

It asks for the least defensible thing. Not learning, not contributing, not networking. An evening spent on something with no value, which is a hard thing to justify to yourself and a harder thing to invite someone else to.

There is no product behind it. Most observances that scale have somebody's interest behind them. This one has nobody's.

What a good version elsewhere would need

If you wanted one for your own community, the parts that seem load-bearing:

A fixed date, arbitrary is fine. The date is the whole mechanism. Something on the calendar converts a good intention into an appointment, and nothing else does.

A one-line rule that forbids usefulness. Not "build what you want" — something that explicitly rules out the justifiable project, because otherwise people build the justifiable project. "Put your best practices away" does this in five words.

A place to show, with a low bar. The single thing Whyday actually lacks. It does not need to be a gallery; it needs to be somewhere a person can post a broken thing without ceremony.

No prizes, no judging, no theme. All three import direction, and direction is what the day is a holiday from.

Somebody who reminds people every year. Unglamorous and decisive. Traditions that persist have a person whose job is remembering, and the ones that die usually died because that person stopped.

The honest position

We are not campaigning for anyone to adopt August 19. Borrowed commemorations feel borrowed, and a Rust community observing a Ruby programmer's disappearance would be a bit odd.

What is worth borrowing is the structure: a fixed day, an explicit prohibition on usefulness, a low-ceremony place to show the result, and one person who remembers. Attach it to whatever your own community actually cares about.

And if it turns out nobody in your language has ever proposed such a thing — that is a project, and it is one evening's work to write the page.

Reviewed August 9, 2026.

The short version