Curiosity, with
a practical streak.

A long time in the web’s engine room.

I’ve spent more than two decades in the education industry, primarily in content and marketing. My long-term work with Beelineweb and Trade-Schools.net connects career research with the technology and processes that get it in front of people.

That means looking at the whole thing: how we research a page, how it gets published, whether people can find it, what they do next, and whether the systems behind that next step actually work.

My day-to-day work spans technical SEO, development, analytics, editorial workflows, internal tools, calculators, and lead-generation integrations. These overlap more than a job title suggests. A content problem can turn out to be a data problem. A conversion problem can turn out to be broken software.

At Trade-Schools.net, I contribute content and help maintain research standards and site updates. Some pages carry my byline; others are collaborative work under the editorial team’s name. My Trade-Schools.net author profile explains that relationship.

Useful beats impressive.

I enjoy finding the dependency someone missed, the number that doesn’t quite make sense, or the failure that keeps recurring because nobody fixed the underlying process.

I’m comfortable experimenting and being wrong. I’m much less comfortable dressing an assumption up as a fact. The interesting part is finding out what actually happened, then making the next attempt better.

Understand the system. Find the evidence. Be clear about what you still don’t know.

The same curiosity comes home.

I’m a father of two and a hands-on homeowner on a rural property in British Columbia’s Okanagan. Our private water supply draws directly from the lake and relies on electric pumping. We also have septic, propane heating, a heat pump, and irrigation to think about.

When the power fails, water can fail too. After outages in both winter and summer, “backup power” stops being an abstract shopping category. It becomes a question about which systems depend on which other systems.

I’ve dealt with leaks, appliance hoses, irrigation problems, a failed water heater, and the joys of suddenly having no hot water. At a previous home, that included basement water issues, leak sensors, and smart-home systems. Networking, temperature monitoring, and general troubleshooting are familiar territory too.

I’ve also lived through Okanagan smoke seasons and nearby wildfire threats with children and pets in the household. We’ve had reasons to get ready, but fortunately haven’t had to evacuate our current home. That experience makes preparation relevant without needing a dramatic survival story.

How that became ReadyHome.

ReadyHome Canada started partly as an SEO and business experiment. I saw an interesting search opportunity and began building around it.

Then I kept finding myself researching problems I actually had—or could reasonably expect to have. Power, pumps, smoke, heating, leaks. The project became a place to turn that investigation into useful Canadian guides and tools.

I’m building it as a researcher, technical operator, and homeowner. My own backup-power setup is still modest: battery packs, not an installed generator or a large home battery. Researching equipment doesn’t mean I own it, and publishing a calculator doesn’t mean I’ve field-tested every scenario.

That distinction matters. I’d like to add documented first-hand testing over time. Until then, the work should stand on its sources, its reasoning, and how honestly it explains its limits.