On February 28, 1901, Linus Pauling was born in Portland, Oregon. He would go on to become the only person to win two unshared Nobel Prizes—one in Chemistry (1954) for his research on chemical bonds, and one for Peace (1962) for his activism against nuclear weapons testing. In an era that increasingly demanded specialization, Pauling did the opposite: he insisted his scientific expertise gave him more responsibility to speak on social issues, not less.
Here's what strikes me about Pauling's legacy for those of us in tech: he never bought into the false choice between being "technical" and being a leader who cares about impact beyond the code. Today's tech landscape loves to put us in boxes—you're either an IC or a manager, either product-focused or technically deep, either building features or thinking about ethics. But the most meaningful work happens when we reject these artificial boundaries. The engineer who asks "should we build this?" is just as valuable as the one asking "how do we build this?" The technical leader who considers societal impact isn't distracted from their job—they're doing it better.
Pauling's career reminds us that mastery in one domain doesn't mean tunnel vision—it means having a platform and credibility to make a broader difference. Whether you're the developer who raises security concerns, the architect who advocates for accessibility, or the CTO who speaks up about AI ethics, you're following in that tradition. The depth of your expertise isn't diluted by the breadth of your concerns. If anything, your technical credibility makes your voice on larger questions more essential, not less.