On the Existence of dev2.johuys.be

J. Huys¹, a rubber duck², and rm -rf³

¹Department of Applied Procrastination ²Desk, left side ³Deceased (see dev.johuys.be)

Abstract. We show that a website called dev2 can exist even though it is not clear that dev1 ever worked. We also show that this page is the most stable release in the project's history, because it does nothing.

1. Introduction

There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors. This site was named dev2, so we made no progress on the second one.

2. Main Result

Theorem 1. This page contains no bugs.

Proof. A bug is code that does something it shouldn't. This page has nothing to do, so it can't do anything it shouldn't. ∎

Corollary 1.1. Adding a feature will introduce a bug. (The proof is left as an exercise to the next sprint.)

Lemma 2 (Schrödinger's Deploy). Until someone opens the logs, the deploy has both succeeded and failed.

3. Experimental Results

Metric	dev	dev2
Uptime	Was alive	Not yet dead
Lines of code	0 (since today)	0 (on purpose)
Open bugs	Gone with it	See Theorem 1
Test coverage	Unknown	100% of 0 lines

4. Interactive Appendix

To reproduce our results, press the button below. Expect a peer review of uneven quality.

References

Turing, A. (1936). On whether this site will ever finish loading. Undecidable.
Gödel, K. (1931). This page is consistent, but you can't prove it from inside the page.
Murphy, E. (1949). Anything that can go wrong will go wrong on Friday afternoon.
Anonymous. (every day). “It's probably DNS.” It was DNS.

Received: 26 October 2026. Accepted: by nobody. Published: here, regrettably.
Funding: none. Conflicts of interest: we wrote this ourselves.