The "Don't Be an Asshole" Theory of Career Growth

article_02.txt

_ □ x

Introduction: The Myth of the Meritocracy

We like to tell ourselves a comforting lie in the tech industry: "If I am just good enough at coding, nothing else matters."

We imagine that if we lock ourselves in a dark room, learn Rust, master Kubernetes, and produce 10x output, the world will beat a path to our door. But that's not how it works.

This is especially true now that AI is rewriting the rules. Technical execution is becoming easier: Agents can generate the boilerplate, refactor the functions, and write the unit tests. What is left for humans?

The answer is connection.

Technical skills are the baseline and price of admission. But as AI raises the floor for technical competence, the ceiling is no longer defined by how fast you code, but by who you know and how you treat them. The multiplier is the social game. And the most critical piece of that game is a concept called Weak Ties.

The Science: Granovetter's Bombshell

In 1973, a sociologist named Mark Granovetter published a paper titled "The Strength of Weak Ties." It is one of the most cited papers in sociology, and it completely changed how we should understand social networks.

Here is the breakdown:

Strong ties: These are your best friends, your immediate family, and your daily teammates. You move in the same circles. You know the same information.
Weak ties: These are acquaintances. The guy you met at a conference once. The project manager from your last job. The person you chat with occasionally on X.

Weak ties theory offers us something counter-intuitive. When it comes to finding new jobs or spotting new opportunities, weak ties work much better than strong ties.

Why? Because people close to you already know what you know. They are in your bubble.

Weak Ties are bridges. They connect you to social circles you don't belong to. They possess information you don't have. Statistically, your next big break is far more likely to come from someone you barely know than from your best friend.

The "Don't Be an Asshole" Perspective

This brings us to the Golden Rule of the social game: Don't be an asshole.

When you realize that "Weak Ties" are the source of opportunity, you realize that every interaction matters.

The junior dev you rolled your eyes at during code review? They might be a CTO in five years.
The person you had coffee with and forgot about? They might remember you when something changes.
The non-technical stakeholder you condescended to? They might be the one deciding whether your project lives or dies.

If you treat people transactionally and only being nice to those who can help you right now, you are burning the bridges that Weak Ties are built on.

My Perspective: The Serendipity of Connections

I know quite a few people, and the trajectory of careers often hinges on random interactions that seem meaningless at the time.

Here is a real example from my own life:

I used to chat with a guy at my local gym. We weren't "friends" in the traditional sense. We didn't hang out on weekends or know each other's life stories. We just had fun, small conversations between sets. He was a nice guy, easy to talk to.

One day, he casually asked if my company had any open positions. As it happened, we did. He asked who he should contact, so I gave him my boss's phone number.

Later, I told my boss: "Look, he seems like a nice person, but I don't know anything about him professionally. I can't vouch for his code, only his character."

I wasn't involved in the interview process at all. He had to prove his technical merit on his own. But guess what? He got the job.

Think about the mechanics of this:

The Weak Tie: If he hadn't been open to chatting with a stranger at the gym, he might have missed out on the open role.
The Filter: Because he wasn't an asshole at the gym, I was willing to share the contact info.
The Result: A connection based on pure social chance resulted in a career change for him and a new hire for us.

He obviously needed the technical skills to pass the interview. I didn't hand him the job. But the access to the job came entirely from a social game played in sweatpants, not a suit.

How to Play the Game (Without Being Fake)

You don't need to be a slimy networker collecting business cards.

You need to cultivate serendipity.

Weak ties don't require intensity. They require light, consistent signals that you're still there.

Be a "Router," not a "Firewall": When you meet someone interesting, ask yourself: Who else should they know? Connect people. Create bridges. The person who links two clusters becomes more valuable than the person who hoards access.
The "Five-Minute Favor": If you can help someone in less than five minutes (an intro, a code snippet, a quick answer), just do it. Don't calculate the ROI. The ROI is the Weak Tie you just strengthened.
Leave Good Artifacts: Most weak ties don't know you personally. They might even just know your pull requests, your documentation, your comments. Those are also social artifacts. Make sure they say, "I'm thoughtful and easy to work with," not "I'm technically right and emotionally expensive."
Check in with no agenda: Once in a while, message that old colleague just to say, "Hope you're doing well." Don't ask for anything. Keep the bridge intact. Don't wait until you need something — by then, the bridge may already be on fire.

Conclusion

Code rots. Frameworks change. The only thing in your career that appreciates in value over time is your network.

You can be the smartest 100x AI engineer in the room, but if you're an asshole, you isolate yourself from the chaos of luck. Weak ties bring luck. They bring the "right place, right time" moments.