TechLove exists to help people solve real problems with technology — not in the abstract, but in the context of how they actually work.
Throughout my career, I’ve been brought in when off-the-shelf technology didn’t quite fit. Sometimes that meant digging deep into systems, limitations, and bugs. More often, it meant integrating tools in a way that respected how a business already operated, instead of forcing people to change how they think or work just to accommodate software.
The constant throughline has been this: I work for humans, not for technology. The business problem stays in focus, even when the technical details get complicated.
stuff here
more stuff here
and yeah more stuff
That perspective was shaped early on. At the start of my career, I helped transition a nursing college from a single computer in the library to a fully networked environment, with a computer on every desk. That work wasn’t just about installing machines and servers — it required creating and delivering training for faculty and administrators so the technology actually became usable.
Later, at MSNBC in Redmond, I made a meaningful contribution to one of the earliest internet content management systems. I wasn’t the product manager or business analyst. What I brought was fluency in two worlds: the developers building the system and the journalists using it every day. Having come from network administration and desktop support, and then working as a journalist myself, I understood both the technical process and the newsroom realities. I could translate between them.
Mid-career, that same pattern repeated at a much larger scale. I worked with a major television network during its transition from linear, tape-based workflows to non-linear, multi-format production destined for broadcast, cable, and streaming. Having once been the person literally moving tapes with a clipboard, I understood the operational constraints. Having spent years listening to chief engineers and business owners, I could spot opportunities for efficiency across the supply chain — from ingest to air to stream.
Alongside larger organizations, I’ve also worked directly with small businesses. As a freelance technologist, I’ve helped a boutique architecture firm extend Wi-Fi coverage across their office, establish practical photo and content management processes, build local presence using Google tools, and begin using search analytics to understand how their work was actually being discovered.
Across all of this, I’ve learned the most from:
- software developers and product managers
- content and workflow experts
- business owners, from sole proprietors to CEOs
Just as important is what I don’t do.
I intentionally stay away from areas like heavy coding and graphic design, focusing instead on integration, systems thinking, and practical problem solving. I don’t work well in environments that require micromanagement — trust and transparency matter. I work openly, explain my thinking, and document what’s been done so someone else can understand it later without having to reinvent the wheel.
If a project or relationship isn’t a good fit, I say that plainly and early, so everyone can move on without friction.
TechLove exists now because there is a growing need for technology problem solving that doesn’t come with expensive overhead, slow response times, or unnecessary complexity. And because this is work I’m good at — helping people feel more confident, capable, and supported as technology continues to change.
