- Authors
- Name
- Edwin Popham
Growing up in the 90s in New Zealand, basketball wasn’t just something I watched—it became part of who I was. The NBA was exploding in popularity, and like everyone else, I tuned in to see the Chicago Bulls dominate. Michael Jordan was the global superstar, the face on every poster and highlight reel. But for me? My eyes were often on someone else—Scottie Pippen.
The Underdog Who Became Essential
Pippen’s story spoke to me. He didn’t come into the league as the next-big-thing. He fought his way up from humble beginnings, and through grit and relentless work, became one of the most versatile players in the game. I played a lot of local basketball back then, and while I admired Jordan’s highlight reels, I connected more with Pippen’s style—the guy who wasn’t always on the front page, but without him, the whole Bulls dynasty would’ve looked very different.
That honesty about the grind—the idea that work ethic and adaptability matter just as much as raw talent—really stayed with me.
The Quiet Force
In a league full of massive egos and bigger brands, Pippen was often content to let others take centre stage. Sure, he had his moments of frustration (who wouldn’t in the shadow of MJ?), but he consistently showed up, defended the toughest assignments, passed first, and did the thankless jobs that made the Bulls so dangerous.
It’s safe to say I learned from that. Not everyone in life gets to be the headline act. But every great team—on the court or in the office—needs people who make others better, even if the spotlight doesn’t shine their way.
Relating It to My Own Story
As a kid, I wasn’t the flashiest player on the local court. I was never going to dunk from the free-throw line. But like Pippen, I learned to value the small things done well: setting a good screen, making the extra pass, digging in on defence. That same mindset has followed me into my career as a software engineer.
In tech, we often celebrate the “superstars”—the flashy feature launches, the hero dev who fixes the big outage at 2am. But what makes systems actually work, and what makes teams thrive, is often quieter: writing maintainable code, mentoring juniors, documenting properly, and moving projects forward as part of something bigger.
Pippen taught me early that you don’t have to be the most visible person to make the biggest impact.
Imperfect, But Reliable
Of course, Pippen wasn’t without flaws. He had very public frustrations and wasn’t afraid to push back when he felt short-changed. But even with all the noise around him, he brought consistency, professionalism, and the kind of versatility every team dreams of. That balance—unselfish yet ambitious, steady even when frustrated—was the thing that stuck with me.
It wasn’t about perfection, but about being someone others could rely on.
When I look back now, I realise why I gravitated to Scottie Pippen. He was the reminder that greatness isn’t always the one who takes the last shot. Sometimes it’s the person who plays every role, sacrifices stats for wins, and keeps the team humming.
As a kid in New Zealand, I cheered a little more quietly for Pippen while most of the world roared for Jordan. And in a way, I still carry that mindset today—whether it’s in sport, family, or engineering. Make the team better, even if you’re not the loudest voice in the room. That’s Pippen’s legacy to me.