About
TrenchOps π
Insights from the tech trenches
About TrenchOps
Field notes, war stories, and brutally honest lessons from the frontlines of IT support, operations, and enterprise tech - written by someone who's still in the trenches.
Who I Am
Lead Support Engineer with more than 20 years of hands-on experience in Silicon Valley's most demanding tech environments. I've worked every layer of the support stack β from first-level tickets at 3 a.m. to complex escalations, from building knowledge systems that actually get used to fighting the single points of failure that appear the moment a key person leaves or documentation goes stale.
This site exists because the most important lessons in tech support and operations never make it into official training materials or glossy conference talks. They are earned the hard way: by being the person everyone calls when everything is on fire, by watching talented teams slowly grind down under toxic dynamics, and by seeing the same preventable disasters repeat across companies that should know better.
I started Support Trenches to document those patterns - and to give the people who actually do the work a clearer map of what they're up against.
Why TrenchOps Exists
The tech industry is obsessed with innovation, velocity, and AI-powered everything. What it rarely discusses with any honesty is the operational reality that makes any of it sustainable - or that quietly destroys customer trust, team health, and company resilience when ignored.
Support Trenches fills that gap with raw, practical, experience-first writing. No corporate theater. No recycled productivity hacks. Just clear-eyed diagnosis of the problems that actually matter in the day-to-day reality of keeping enterprise systems and customers functioning.
The goal isn't to vent. It's to help good people make better decisions - whether that's fixing a broken process, protecting their own energy and integrity, or knowing when it's time to leave a place that punishes honesty.
The "Power Horses" π
You'll see the term power horses throughout these pages. It refers to the high-performing, reliable professionals who carry disproportionate loads in tech organizations:
- The ones who actually fix things when they break
- The ones who document what everyone else ignores
- The ones who mentor juniors and absorb the shocks so the rest of the org can keep moving
- The ones leadership relies on but rarely protects or rewards proportionally
These are the backbone of any functional tech organization. They are also the most at risk of burnout, quiet quitting, or being quietly managed out when they finally push back against broken systems.
This site is written especially for them β and for anyone who leads or depends on them.
What You'll Find Here
𧨠Toxic Workplaces & The Honesty Tax
Why consistently telling the truth often carries a real career cost in many environments - and how to navigate it without destroying yourself or your integrity.
π§ The Human Side of Support
Imposter syndrome in experienced engineers, professional boundaries with coworkers, annual review ritualsΒ as theater, and protecting your energy as the reliable one.
π Support vs. Marketing Reality
Why brilliant products fail after the sale. The math of customer retention. AI tools that create more tickets than they resolve. The gap between hype and operational truth.
π§© Knowledge & Resilience
Single points of failure, documentation that actually survives personnel changes, and building systems that don't collapse when one key person is out sick or leaves.
β‘ Productivity That Matters
Cutting through corporate noise, "hamster wheel" busywork, and performative productivity to focus on the work that actually moves the needle.
π‘οΈ Power Horse Playbook
Strategic advice for high-performers who want to stay effective without becoming the person everyone exploits or the one who quietly burns out.
The Tone & Promise
Candid. Practical. Occasionally irreverent. Always grounded in real frontline experience rather than theory or recycled LinkedIn wisdom.
I don't pretend to have all the answers. But after two decades in the trenches, I have seen the patterns that repeat across companies, roles, and economic cycles. My hope is that by naming them clearly, fewer talented people have to learn every painful lesson the hard way.
If any of this resonates, welcome to the trenches. The comments on every post are open - share your own stories. The more real and specific, the more valuable this space becomes for everyone.
Contact
In case you want to reach me - for example if you have interesting stories to share from the tech trenches, then click the button below.
{{contact-email}}
TrenchOps π
0 comment(s)
No comments yet. Be the first to comment.
Leave a comment