This site looks like a 1994 dial-up server. That’s deliberate, and it isn’t just nostalgia.
The obvious argument
I started in IT at a time when you called machines with a modem, when the welcome screen was drawn character by character, and when a well-composed NFO file was a signature. That world shaped how I work: constraints accepted on purpose, every byte justified, documentation cared for because it was the only interface.
An infrastructure consultant who presents their work in a bought template says something about themself. I preferred to say something else.
The less obvious argument
The constraint has measurable consequences:
- 80 columns. Everything fits on a character grid. No layout breaks at an unexpected width, because there’s only one.
- Sixteen colours. The EGA palette, nothing else. No swatch to maintain, no debate over the exact shade of a button.
- No cookies, no analytics. There’s nothing to consent to, so there’s no banner to show.
- Readable without JavaScript. Effects are optional layers. Turn off scripts: the content stays intact.
- Plain mode. A footer button turns off the effects. If you came here looking for information, you shouldn’t have to sit through a demo.
A site that follows these rules loads fast, reads everywhere, and ages well. That’s exactly what I try to deliver when someone hands me an infrastructure.
The limit
I know the objection: this stance doesn’t speak to everyone. True. A client looking for an interchangeable vendor won’t stick around here, and that’s fine. The rest of the time, IT work gets chosen on trust, and trust starts with knowing who you’re talking to.
Now you know.