It’s 2000. I’m sitting at my computer, squinting at lines of HTML code that make absolutely no sense. My wife’s in the next room, dealing with another flare-up of her chronic illness, and I’m thinking maybe this whole internet thing could give us both something meaningful to do together.
I had no idea I was about to spend the next quarter-century obsessed with the web.
The Madness Begins: 1,000 Pages and Counting
Most people start with one website. Not me. I dove headfirst into what can only be described as digital hoarding: 178 domain names and over 1,000 hand-coded pages. Every single one typed out character by character, no shortcuts, no templates. You can read about those early days of computing in more detail.
Was it excessive? Absolutely. Was it necessary? Probably not. But I was working at Trader Joe’s, pulling in steady income, so these weren’t money-making schemes. They were pure experimentation. Little digital laboratories where I could break things, fix them, and break them again.
My wife found purpose in these projects too. On days when her illness kept her bedridden, she’d help me brainstorm content, edit copy, or just bounce ideas around. Those websites became more than code. They became our shared creative outlet during some tough times.
When Affiliate Marketing Actually Worked
Then came Internet-Tips, my entry into making actual money from websites. Hundreds of articles, all hand-coded because WordPress was still this weird blogging thing that “real” developers didn’t take seriously. I was completely wrong about that, but we’ll get to that disaster later.
The site became my laboratory for understanding what people actually wanted to read online. I wrote about everything from email etiquette to browser optimization, from HTML tricks to internet safety. Each article was built to solve a real problem, and slowly, people started finding value in what I was creating.
The affiliate commissions started small. A few dollars here and there from software recommendations and web hosting referrals. But those first checks felt like validation that this crazy internet thing might actually have legs. More importantly, I was learning that helping people solve problems was more rewarding than showing off technical skills.
Internet-Tips taught me that the best websites aren’t about the creator. They’re about the reader. Every article had to earn its place by being genuinely useful. That philosophy shaped everything I built afterward.
I also went completely overboard with a photography site, writing scripts that generated hundreds of thousands of pages automatically. The photos themselves were a passion project: 300,000 images I’d captured at Renaissance faires and belly dance performances across the country. Every weekend was another event, another opportunity to document these vibrant communities that most people never see.
Then disaster struck in the most terrifying way possible for any digital creator.
The Great Hard Drive Crisis: A Month of Digital CPR
One morning, my main storage drive started making sounds that no hard drive should ever make. Not the gentle whir of normal operation, but this grinding, clicking noise that made my stomach drop. This wasn’t just any drive. This was the drive. Three hundred thousand irreplaceable photos spanning years of work. (This has since grown to 950,000 photos, all on my photography site.)
I ran to the computer store like my house was on fire and bought the biggest, fastest drive I could afford. This was back when drives were slow, expensive, and the idea of cloud backup was still science fiction. I rushed home and started copying files, praying I wasn’t too late.
I wasn’t fast enough.
The drive crashed with a screech that sounded like digital death. Hours of work, years of memories, potentially gone forever. But I’m stubborn, and I wasn’t giving up that easily.
Through some combination of luck and desperation, I discovered that if I let the drive cool down completely, it would work for exactly twenty minutes before overheating and dying again. Twenty minutes of copying, then an hour of cooling. Twenty minutes on, hour off.
For an entire month, I lived by this rhythm. I’d set timers, copy frantically during the good twenty minutes, then pace around my house during the cooling period like an expectant father. My wife thought I’d lost my mind, watching me babysit a dying hard drive with the dedication of a trauma surgeon.
Some files were too damaged to save. About a thousand photos had literal holes in them: corrupted sectors that left digital scars across dancers’ faces and festival scenes. Those images are a permanent reminder of what happens when you get complacent about backups.
That crisis changed everything about how I handle data. I developed backup systems with multiple redundancies and offsite storage long before it was standard practice. I wrote about the full experience in The Cascade Disaster.
The Great WordPress Disaster of 2013
After leaving Trader Joe’s in 2013, I decided to get “professional” with WordPress. The result was a website so spectacularly hideous it could’ve been used as evidence in a design crime trial.
Neon colors that literally hurt to look at. Electric lime green backgrounds with hot pink text. Spinning graphics everywhere because apparently I thought my visitors needed motion sickness with their content. Text that blinked like a broken neon sign at a roadside diner. And plugins. I installed everything that looked remotely interesting, whether it served a purpose or not.
The site loaded slower than dial-up because I’d crammed it full of widgets, counters, weather displays, stock tickers, and animated cursors. I even had music that auto-played because clearly what everyone wanted was to be aurally assaulted the moment they visited my site.
My wife took one look at it and asked if I was feeling okay. Friends politely suggested I might want to “tone it down a bit.” Even I couldn’t stand to look at it for more than thirty seconds, but I was convinced this was what “professional” web design looked like.
It was embarrassing. It was unprofessional. And it was exactly the faceplant I needed to learn what not to do. Sometimes you have to fail spectacularly to understand what success actually looks like.
Finding My Identity: The Writing King Era
From those garish ashes rose something better: The Writing King. I’d finally found my brand, my voice, and most importantly, some actual design sense. Built on RTTheme, a clean framework that felt like stepping into a well-lit room after being trapped in a disco ball factory.
The beauty of RTTheme was its restraint. Clean typography, sensible spacing, colors that didn’t assault the retinas. It was everything my previous site wasn’t, and visitors could actually stay long enough to read my content without developing migraines.
WordPress was simpler then too. You could actually understand what every plugin did without reading a manual. Themes didn’t require computer science degrees to customize. The WordPress community felt more like a helpful neighborhood than the sprawling metropolis it’s become.
I started taking client work, building custom websites with themes like OnePageExpress. Clean, functional, effective. My clients were happy because their sites actually worked. I was happy because I was finally creating things I could show off without apologizing. And slowly, I was becoming someone who actually knew what they were doing.
Each project taught me something new about balancing client needs with technical possibilities. Some wanted every bell and whistle. Others just needed a simple, professional presence. Learning to match the solution to the actual problem, rather than showing off every technique I knew, was a turning point.
The Endless Quest for Digital Perfection
My website has been through more makeovers than a reality TV show. Six major theme overhauls and probably a hundred plugins tested, installed, cursed at, and deleted. Each change taught me something new, either about what I wanted or what I definitely didn’t want.
This wasn’t vanity. It was education. Every new theme was a lesson in design philosophy. Every plugin was a lesson in functionality versus bloat. Every redesign brought me closer to understanding what makes a website actually work.
The Elementor Revelation
Then I found my holy grail: Elementor with a minimal theme foundation. Like finding the right tool after years of struggling with the wrong ones.
Here’s why it changed everything:
- Visual editing that actually works: I can see exactly what I’m building without constantly switching between editor and preview modes.
- Responsive controls that don’t fight me: Mobile, tablet, desktop, all handled without cryptic CSS media queries.
- Typography that doesn’t require a PhD: Font pairing, spacing, and hierarchy controls that just make sense.
- Custom CSS when I need it: Sometimes you need to go under the hood, and Elementor doesn’t lock you out.
- Templates that inspire instead of limit: Starting points that spark ideas rather than cage them.
- Performance that doesn’t suck: When optimized properly, it’s fast.
- Widget ecosystem that solves real problems: Every addition serves a purpose, not just decoration.
This combination changed how I build everything in WordPress.
WordPress Mastery: Beyond User to Expert
Twenty-five years in, I don’t just use WordPress. I speak its language. Custom post types? Done. Performance optimization? I can make your site load faster than your competition loads their homepage. Security hardening? Your site will be locked down tight.
But here’s what actually matters: I understand that behind every website is a person with a story to tell, a business to grow, or a dream to get off the ground. The technical stuff is just the foundation. What matters is when the technology serves the purpose.
I’ve watched WordPress grow from a scrappy blogging platform to the engine powering nearly half the internet. More importantly, I’ve grown with it, learning not just what’s possible but what’s practical, sustainable, and useful.
What Twenty-Five Years of Digital Battle Scars Means for You
I’ve sat through month-long hard drive death watches. I’ve built websites so ugly they could clear a room. I’ve hand-coded over a thousand pages when five would have done the job. I’ve installed plugins that broke everything and themes that made visitors question my sanity.
Most developers learn from tutorials and Stack Overflow. I learned from catastrophic failures at 3 AM when client sites went down, from losing irreplaceable data, from watching years of work disappear. Every disaster taught me something that no course or certification ever could.
When you work with me, you’re getting someone who’s been through the wars and came out with strategies that actually work. I know which plugins will slow your site to a crawl before you install them. I can spot theme problems that won’t show up until your traffic spikes. I build backup systems that would survive anything because I’ve lived through data loss that nearly ended everything.
After all these years, I still get excited about building something that works. Your project isn’t just another website to me. It’s the next chapter in a story that started with broken HTML and led to genuine expertise.
Twenty-five years of learning what works, what doesn’t, and what makes the difference between a site that gets lost in the noise and one that changes everything for your business.
Your story deserves that kind of experience behind it. Let’s build something that works as hard as you do.