The Christmas Commit

December 25th, 2025. 11:47pm. While the rest of the household was debating whether Die Hard qualifies as a Christmas movie (it does, and this is not up for discussion), someone opened a terminal and typed:

npx create-next-app@latest revend

The first commit happened at 11:52pm. It contained a Next.js skeleton, a default layout, and a hero section that said "The Operating System for ITAD." The hero section would be rewritten the next morning. And again the day after. And approximately forty-seven more times over the following months. If there's one thing that's constant in software development, it's that the first version of the hero section is never the final one.

Why Christmas Day

Not because of urgency. Not because of a deadline. Because the idea had been circling for months, and at some point you either start or you don't, and the specific day you start doesn't matter as much as the fact that you started. December 25th is as good a day as any. Better, actually, because nobody sends emails on Christmas Day, and the absence of emails creates a rare pocket of focus in which an entire project scaffold can be born.

The idea behind ReVend was not complicated: ITAD operations run on tools that weren't built for ITAD. ERPs that don't understand pallets. FileMaker databases that one person can modify. Excel spreadsheets that serve as the backbone of a billion-euro secondary market. WhatsApp groups that function as trading floors. Every ITAD operator knows this. Everyone at the conference bar agrees. Nobody had built the alternative.

The gap between "everyone agrees this should exist" and "someone actually builds it" is measured in years and excuses. The Christmas commit was the end of the excuses.

What Came After

January was ugly. The prototype had a sidebar, a dashboard, and dark mode. It looked like every other SaaS template on the internet. It worked correctly. It was absolutely devoid of personality. But it proved the concept: you could build a single interface that tracked assets, managed warehouses, handled grading, and connected to the sales flow. Not as four separate tools. As one.

February was the deep clean. Code cleanup, dependency updates, removal of decisions made at 2am that seemed brilliant at 2am but were not, in fact, brilliant. The kind of technical debt that accrues in the first weeks of a project when speed matters more than structure. February was when structure caught up.

March was when it got real. The database awakened. Mock data gave way to real tables, real queries, real foreign key relationships. Assets got serial numbers that persisted. Grades got structure. Warehouses got zones. The platform stopped being a demo and started being software.

The Versioning Philosophy

Every version got a subtitle. Not because subtitles are necessary, but because naming things forces you to articulate what changed and why it matters. "The Warehouse" (v0.2.0) was about the first floor views. "Assembly Line" (v0.3.0) was about testing workflows. "The Database Awakens" (v0.16.0) was about the migration from mock data to Postgres. "The Great Migration" (v0.20.0) was about finishing what v0.16.0 started.

The changelog reads like a novel. Not because we're precious about it, but because a changelog should tell you the story of a product. What we built. Why we built it. What we learned while building it. If you can't explain your changelog to a customer, you can't explain your product.

What We Learned

Starting is easy. Continuing is hard. The Christmas commit took five minutes. The next three months took everything else. The commitment isn't in the first line of code. It's in the 500th commit, when the work is no longer new or exciting but merely necessary, and you do it anyway because the problem you're solving hasn't gone away.

The ITAD industry still runs on spreadsheets. The WhatsApp groups still have 187 members. The stock lists are still outdated by Thursday. The auditors still arrive to find documentation in four different systems. The FileMaker tax is still being paid. Nothing about the problem has changed. Which means everything about the solution is still needed.

---

December 25th, 2025. A terminal. A command. A commit message that said "initial commit" because every project starts with "initial commit" and nobody has ever come up with a better name for the beginning of something.

The hero section said "The Operating System for ITAD." It was rewritten the next morning. Some things in software never change. Starting is one of them.