There’s a very real, very stupid, and very darkly hilarious truth about working in web development that nobody talks about openly. The guy who builds, maintains, optimizes, secures, and rescues everyone else’s websites… is usually committing unspeakable crimes against his own. And yes, before anyone says it — I know. I are bad, Lucas. I accept this. I live this. I am this cautionary tale.
But let me explain how this level of professional hypocrisy happens, because it doesn’t come from laziness. It comes from survival.
My clients’ websites? Oh, they’re pristine. Updated. Patched. Hardened. Backed up. Search engine optimized. Mobile optimized. Performance tuned. If a plugin sneezes wrong, I know about it before it finishes the inhale. Their infrastructure is clean enough to eat off of. Meanwhile, my own company site — https://osmondtech.com/ — has been sitting there like a digital time capsule since 2014. Not “retro.” Not “vintage.” More like “archaeological.” At this point, if you dig through the code you’ll probably find a fossilized Internet Explorer compatibility fix and a note about Google+ integration.
And it’s not like I didn’t know it needed updating. I knew. I always knew. Every time I logged into cPanel. Every time I updated a client site. Every time WordPress released a major version and I thought, “Huh… I should probably do that too.” But here’s the thing about running a web company — your own stuff is always last. Client emergencies come first. Revenue work comes first. Deadlines come first. Fires come first. Your own site gets whatever scraps of time are left over, which usually means none.
The ironic part? The new site was already built. Or mostly built. Sitting on my server like a fully packed suitcase waiting for a trip that never got booked. Structure done. Design done. Services rewritten. Modern stack. Accessibility updates. The works. About 90% finished. Just needed copy tweaks, polish, and a launch push — you know, the last 10% that somehow takes 90% of your will to live.
So what did I do? I ignored it. For months. Maybe longer. Because “I’ll get to it” is the battle cry of every web developer neglecting their own infrastructure while heroically maintaining everyone else’s.
And then… I did what every seasoned professional eventually does. I broke the old site.
I don’t even remember what I was doing. Probably poking around in some outdated plugin that hadn’t been touched since Obama’s first term. Maybe updating something. Maybe removing something. Maybe just breathing near it wrong. But whatever it was — boom. White screen. Dead. Flatlined. No warning. No error message. Just the digital equivalent of the engine falling out of a moving car on the highway.
Now normally, that’s fixable. Except remember — last major update: 2014. We’re talking ancient WordPress core. Outdated PHP. Plugins held together with digital duct tape and prayer. Trying to debug that would’ve taken the next eight hours of my life — minimum — just to find the hole in the hull. And even if I patched it? I’d still be sailing a ship that should’ve been scrapped years ago.
So I sat there, staring at the corpse of my own website, and had what can only be described as a moment of professional clarity mixed with mild self-loathing. Option one: Spend the entire day resurrecting a digital relic that no longer represented my business anyway. Option two: Say screw it and finally launch the new site that was already 90% done.
You already know which path I chose. Because at some point, you stop patching the old haunted house and just move into the new one that already has electricity.
Now — fair warning — there’s probably still some redundant copy floating around on the new site. Maybe a service description that overlaps. Maybe some phrasing that needs tightening. I’ll get to it… right after I’m done helping change the music industry.
Priorities.
So for anyone who’s ever wondered what my day job actually is — this is it. Building sites. Fixing infrastructure. Consulting. Accessibility adaptation. Hosting architecture. Media integration. Basically living at the intersection of technology and “how do we make this actually work without catching fire.” The new site finally reflects what I actually do today instead of what I did a decade ago.
Moral of the story? If your web developer’s own website looks slightly neglected, it’s not because they’re bad at their job. It’s because they’re too busy doing it for everyone else. That — and occasionally crashing their own ancient production site while wandering the backend like a sleep-deprived raccoon.
But sometimes breaking the old thing is exactly what forces the new thing to finally go live. And honestly? It was way past time.
Have something to say? We welcome your comments below — this is where the real conversation happens.
Each blog post is shared across our social transmitters, but those are just bigger antennas. The original source — and the signal we control — is right here on the blog. If you’re looking for other ways to stay updated on Rolling with Scissors, you’ll find our official transmitters linked below.
Spin the dial — we’re probably on it. Lock onto your frequency. Pick your favorite antenna below and ride the signal back to us.