It’s a fair question. “First a blog, now a podcast? When do you actually sleep?”
If you look at my browser history or the notes app on my phone, you will see a graveyard of half finished thoughts. There are technical diagrams for CUCM to Webex migrations that never saw the light of day, scripts for the perfect podcast that I sat on for years, and GitHub repos that I was too nervous to make public. For a long time, I was a professional over thinker. I was the guy who wanted to make sure the outline was perfect before the first word was ever typed. I wanted the lighting to be right, the audio to be studio grade, and the arguments to be bulletproof.
I was waiting for a version of myself that did not exist: and likely won’t.
But earlier this year, I decided to lean into a new theme: doing uncomfortable things. I realized that the “perfect” version was just a sophisticated form of procrastination. The world of modern communication moves too fast for perfection. If you wait until you are 100% ready, it’s already too late.
That shift meant moving away from the safety of “planning to do” and moving into the messy, public reality of “doing.” It resulted in two specific corners of the internet: Writing and Podcasting.
If you have landed here, you might be wondering why a Practice Lead for Collaboration at a company like Precision Computer Services (PCS), someone who spends his days working on CUBE integrations, cloud contact center deployments, and A/V room designs, is spending his personal time writing about fax machines and recording long form conversations with traders and OSHA experts.
This isn’t some long game of building a brand or hitting a content schedule. It’s about the search for the quiet in an increasingly noisy world. It’s about why we do what we do, and more importantly, how we keep our humanity intact as the systems we build get more complex.
The Blog: Where Ideas Go to Be Stress Tested
I have always believed that if you cannot explain a concept simply, you do not actually understand it well enough. In the world of enterprise technology, we are surrounded by people who hide behind jargon. We have all been in those meetings. Someone uses terms like “Cloud Native,” “AI Driven,” or “Transformational Synergy” as a shield to mask the fact that they do not actually know how the packet gets from point A to point B. They are selling the magic, without respecting the mechanics.
Writing is high friction. It’s a slow, deliberate process. Unlike a conversation where you can use hand gestures and “you know what I mean” to skip over the gaps in your logic, writing forces you to be precise. You cannot hand wave an idea when you are typing it out for a public audience. You have to commit. If something does not make sense on the screen, it probably does not make sense in your head.
The Problem of the Vending Machine Culture
When I wrote the post Operators != Engineers, I was processing a frustration I have seen in our industry for a decade. We are in the middle of a quiet crisis. We are training a generation of people to be “vending machine” operators.
A vending machine operator knows which button to push in a GUI to get an outcome. They know that if they click “Provision User,” a phone will eventually ring. But if things break, they are lost. They do not know the protocol, they do not understand the dial plan, and they have no concept of the signaling happening behind the scenes. As long as the GUI works, they look like experts. When it doesn’t, they are just observers.
Writing that post forced me to define what I call the Skill Cliff. It’s the moment where the automation stops and actual engineering intuition begins. In the enterprise world, the Skill Cliff is where the most expensive mistakes happen. It’s where a 10 minute outage turns into a 10 hour outage because no one on the team understood how anything worked. GUI experts.
I promise I’m not just venting. I’m creating a framework that I now use when I am mentoring others. If I had not forced myself to sit down and write those words, that idea would have remained a vague construct. Now, it’s a standard.
The Value of the Antiquated
But the blog is not just for heavy technical theory. Sometimes it is a place to defend the things we love to hate. Take the humble fax machine. On April 15th, as the world was scrambling through paperwork, I posted a piece about why we all hate fax machines and you can’t tell me otherwise.
Most people in tech view the fax as a punchline. But if you look at it through the lens of legal binding, security, and verifiable communication, you start to see why hospitals and law firms still cling to it. The fax machine provides a “handshake” that is incredibly difficult to spoof in the same way an email or a digital file can be.
That is usually the thread I am pulling on when I write:
- Why does this still exist?
- What problem is it actually solving?
- What is the human intent here?
Often, the “outdated” solution is still around because it solves a human problem that the “modern” solution has not quite mastered yet.
The Podcast: Finding the Human in the System
If the blog is the laboratory where I try to organize my own thinking, the podcast is the trading floor.
I started it because a lot of the people doing the most important work are not the ones talking about it publicly. They are the ones in the middle of the system, making sure things hold together. They are the “quiet builders” who make the world move.
I wanted to capture the nuance that text misses. You can read about the intensity of a New York trading floor, but hearing someone like Noah Holzberg talk about the reality of it changes how you think about something like uptime. It stops being a percentage on a dashboard and starts being something with real, immediate consequences. You hear the weight of the decisions and the passion that make those decisions possible.
The Uncomfortable Recording Session
The podcast was my ultimate “uncomfortable thing.” For years, I told myself my voice was not right or that I did not have enough “big name” guests to launch. Finally, I just stopped outlining and started doing. Instead of planning it into perfection, I hit record.
Since then, the conversations have taken me into areas I did not expect. Talking about safety with OSHA, or about psychology and systems with people like Philip Lemaster, starts to blur the line between “technology” and everything else.
You realize pretty quickly that most of what we build is really about people, even when it does not look that way on the surface. We are building the nervous system of society. When it works, it’s invisible. When it fails, everything, the economy, the healthcare system, our personal relationships, stops. The podcast is my way of making the invisible, visible.
Why Both?
People ask why I don’t just pick one. The reality is that the blog and the podcast represent the two different ways we process reality.
- The Blog is where I slow down. When I am writing, I am an engineer. I’m looking for logic, code snippets, and reproducible results. If I’m talking about an MCP server for Webex Calling, you need the API calls and the diagrams.
- The Podcast is where I speed up. When I am recording, I am a collaborator. I’m looking for the “why.” I want to hear the hesitation in a safety expert’s voice when they talk about the limits of automation.
To me, the two formats are a feedback loop. An idea usually starts as a technical experiment at my desk. I might build a tool to simplify administrative overhead, like querying full organization user data or pull call history details. I will write a post about it to document the GitHub repo and the logic. That post often sparks a conversation on LinkedIn or in a meeting. Someone will say, “I saw your post on automation, but how does this change the way our team actually works day to day?”
That question then becomes a podcast episode. We move beyond the code and talk about the cultural shift. We talk about whether reducing administrative effort actually frees up budget for strategic work. The blog provides the structure, but the podcast provides the soul. One validates the other. Without the blog, the podcast might get too abstract. Without the podcast, the blog might get too cold.
The Intersection of Collaboration and Curiosity
At my core, I am a builder. I have always been the person who wants to know how things work. Whether I am building a hybrid video meeting space for a client at PCS or building a side project like Whatever, You Pick, I am obsessed with friction.
My day job is about strategy and execution. At PCS, I lead our collaboration practice. We help customers modernize. We take them from legacy on-prem CUCM environments to the cloud. We build cloud contact centers that actually work the way people do. It’s high stakes work. When a contact center for a major client goes down, people’s lives are impacted.
But LutzTalk is the broader umbrella for the things that do not fit into a standard Statement of Work. It’s the outlet for the “Why is this still the way we do things?” questions.
Delegation is the New Interface
We are currently moving into an era where Delegation is the New Interface. This is a concept I have been chewing on for months. For the last thirty years, our interaction with technology has been about “input.” We click, we drag, we type. We are the ones doing the work, and the software is the tool.
Now, we are moving to a world where we assign outcomes. We define our intent, like “I need a summary of this meeting” or “Migrate these users to the new location,” and we expect the system to execute.
This shift is useful, but it changes what it means to understand what you’re working with. The organizations that win in this new era will not be the ones that adopt AI the fastest; they will be the ones that redesign their workflows and prove that what they have delegated is actually producing results. If you rely entirely on the system without understanding it, you are in a different kind of position than you were before. You have moved from being an engineer to being a passenger.
Staying Hands-On in an Automated World
As more of this gets abstracted, it becomes easier to lose the underlying intuition. That is one of the reasons I still stay close to the technical side of things.
Even as a Practice Lead, I am hands-on with SIP, CUBE, and A/V systems. I work closely with customers and internal teams to standardize best practices, simplify dial plans, and enable migrations. I still look at Room Series and MTR style environments.
It’s less about staying busy and more about staying connected to the reality of the work. LutzTalk is an extension of that. It’s a place for people who want to understand what is happening underneath the surface, not just interact with the interface. It’s for the person who sees a “vending machine” solution and wants to take the back panel off to see the wiring. It’s for the engineer who is tired of being told “it just works” and wants to know how it works.
Sometimes, that curiosity solves small, personal frictions too. I built Whatever, You Pick because the “where should we eat” conversation was a system failure in my own life. It was 10 minutes of wasted time every single night. The scale is different from a global trading floor, but the thought process is the same: identify the friction, understand the system, and build a better way.
If you are reading this and want to skip the dinner debate, message me “HANGRY” for free premium access. It’s a small thank you for being a fellow traveler in this quest for clarity.
The Bottom Line
So, why am I doing this?
Part of it is to hold myself accountable to actually understanding the things I work on. Part of it is to document the work of people who do not usually get a spotlight but are doing meaningful, complex work. And part of it is just to have a place to think through how all of this is changing.
Writing and recording forces me to slow down enough to process the shift toward automation and AI without losing the human element. It keeps me from getting stuck in the habit of just planning things instead of doing them.
The world of 2026 is moving faster than ever. The systems are more complex, the jargon is thicker, and the “vending machines” are more polished. I am just trying to make sense of a small part of it.
Whether you are here to find a technical solution, to hear how a trader handles data density, or to understand why your office still has a fax machine, we’re just getting started:
Over the next few months, we have a lineup of guests that reflect that same obsession with the systems that run our world. I’ll be sitting down with Matt Parker from PrizePicks to go under the hood of one of the fastest growing platforms in sports tech, exploring how they manage massive data density and real time user engagement. I’m also talking with Chad Patterson from Cisco, whose work the last decade covers the shift from on-prem hardware to cloud-driven software. And for a change of pace, Sam Gault from Edward Jones will join me to discuss the human systems behind wealth management and how financial frameworks mirror the engineering principles we use every day. These are the builders and thinkers who understand that whether you’re moving packets or portfolios, the architecture matters.