How Tech Acceleration Forced a Rethink of My Personal Infrastructure
I wasn't trying to build a 'Personal OS.' I just didn't want to keep paying for a website nobody visited. But one cost optimization led to another.
Projects, hobbies, and how I think
I wasn't trying to build a 'Personal OS.' I just didn't want to keep paying for a website nobody visited. But one cost optimization led to another.
A few months ago, I was the skeptic rolling my eyes at AI demos. But something shifted when I started using it for my own problems.
I got a $348 renewal notice for a website that maybe 10 people visited last year. So I rebuilt it myself and now pay $0 a year.
I wanted automated alerts when tee times opened up at my golf course. I didn't know how to build it—but I figured it was possible.
I talk about the Raspberry Pi quite a bit. For anyone who's ever thought 'I kind of want to build stuff, but I'm not technical'—these little machines might be your new favorite tool.
Why scroll Google Maps manually when you can script it? How I automated lead generation for local service businesses.
I've always had a low tolerance for people who are just critical. The best question I ever heard in a meeting changed how I think about feedback.
Before I was optimizing workflows or building self-hosted systems, I was a kid obsessed with audio equipment. How my early obsessions shaped how I think about systems today.
I thought buying a camera was the hard part. Then I discovered photography isn't a camera problem—it's a systems problem.
Lessons and experiences from my professional roles
Picture this: You're in a Monday sector meeting with some of the smartest investors in the valley. Each gives 10-minute preambles before getting to their question. Here's how I fixed that.
Kevin was drowning. 150-200 investments, manual tracking, board decks flooding in every month formatted differently. Here's how we built a scalable monitoring system.
Working in venture changed how my brain works. Not because of what they were investing in, but because of how they think.
Every team had become their own mini-intelligence operation. Marketing, IR, Talent, BD, Finance—each tracking their own version of reality. None of it connected.
I burned $100K on a quoting tool that never launched. It became a punchline. Here's what that mistake taught me about systems thinking.
Quarterly business reviews had turned into disasters. Here's how I built a reporting system that transformed chaos into strategic conversations.
There's a kind of interview that isn't really about the job. It's about whether you can hold the room when everyone's watching.
Unpaid bills. Months of mounting charges with no payment in sight. Here's how I built a systematic fraud detection system that recovered hundreds of millions in uncollectable bills.
I thought enterprise sales was about selling. I learned it was about building a personal marketing organization at scale.
I thought being an analyst meant creating dashboards. I discovered I was actually becoming a human data pipeline in a family-owned berry empire held together by Excel macros.
Your engineering team—the people building your actual product—are spending their days on customer support calls. Here's how I fixed it.
I thought consulting was about having the answers. What I discovered was the opposite: consulting is about being a professional question-asker who helps organizations understand themselves.