What 27 Years in Tech Taught Me About People

The Code Was the Easy Part

I started in tech in 1999. I've been a systems admin, a consultant, a solutions architect, and a builder. I've worked in enterprises, startups, and everything in between.

The technical skills got me in the door. The people skills determined everything that happened after.

Lesson 1: Nobody Cares How Smart You Are

Early in my career, I thought being the smartest person in the room was the goal. I'd over-explain solutions, use jargon to prove competence, and get frustrated when people didn't see what I saw.

That approach failed constantly. Not because I was wrong technically, but because being right doesn't matter if nobody listens to you.

The best technologists I've worked with explain complex things simply. They meet people where they are. They translate between business language and technical language without making anyone feel stupid.

I learned this the hard way in a meeting where I presented a technically perfect architecture to a CIO who cared about one thing: will this reduce our risk of a breach? I spent 20 minutes on the wrong thing. It took me years to stop making that mistake.

Lesson 2: Politics Isn't a Dirty Word

I used to think office politics was something to avoid. Just do good work and the right things will happen.

That's naive.

Politics is just the word we use for how humans make group decisions. Understanding who influences whom, who has budget authority, who feels threatened by change. That's not manipulation. That's awareness.

In enterprise consulting, I've watched technically inferior solutions win because the vendor understood the political landscape. They knew which stakeholder needed to feel ownership. They knew which director's concerns needed addressing before the meeting, not during it.

Ignoring politics doesn't make you principled. It makes you ineffective.

Lesson 3: Trust Is Built in Small Moments

The big gestures don't build trust. The small ones do.

Showing up on time. Following through on the thing you said you'd do. Admitting when you don't know something instead of bluffing. Sending the status update without being asked.

I've worked with brilliant people I didn't trust because they were unreliable on small things. And I've trusted average performers with critical work because they were consistent.

Consistency beats talent in every professional relationship I've ever seen.

Lesson 4: The Resistance Is Usually Fear

When a stakeholder pushes back on a project, the stated reason is rarely the real reason.

"The timeline is too aggressive" often means "I'm afraid this will fail and I'll be blamed." "We need more analysis" often means "I don't understand this well enough to approve it." "Let's table this" often means "I don't want to make this decision."

Learning to hear what people actually mean, not just what they say, changed how I approach every conversation. Instead of arguing against the stated objection, I address the underlying fear. That's when things move forward.

Lesson 5: Your Network Is Your Actual Career

Every major opportunity in my career came through a relationship. Not a job board, not a recruiter, not a cold application.

Someone I worked with five years ago remembers that I delivered. Someone I helped with a problem they were stuck on calls me when they have budget for a project. Someone I was honest with about a risk trusts me enough to bring me into their next company.

Your reputation travels faster than your resume. Every interaction is either building or eroding it.

Lesson 6: Communication Is the Whole Job

I used to think communication was a soft skill. Something nice to have alongside the real work.

Now I believe communication IS the work. The technical implementation is a subset of it.

A solution nobody understands doesn't get funded. A migration nobody was prepared for causes panic regardless of how well it was executed. A security improvement that wasn't communicated properly creates resentment instead of trust.

The best engineers I know spend as much time on documentation, stakeholder updates, and clear explanations as they do on code.

Lesson 7: Knowing When to Shut Up

This took me the longest to learn. Not every meeting needs my input. Not every problem needs my solution. Not every silence needs to be filled.

Sometimes the most valuable thing you can do is listen. Let someone else arrive at the conclusion. Let the quiet person in the room speak.

The senior move is knowing when your voice adds value and when it just adds noise.

What This Means Practically

If you're early in a tech career, here's what I'd tell you.

Learn the technical skills. They matter. But invest equally in understanding people. Learn to write clearly. Learn to present without jargon. Learn to listen for what's not being said.

The people who advance furthest in this industry aren't the best coders or the best architects. They're the ones who can build things AND build trust. That combination is rare, and it's valuable everywhere you go.

After 27 years, the technology changes constantly. The human dynamics haven't changed at all.