Ego Is Not a Flaw, It Is a Disaster
But I tell you, do not resist an evil person. If anyone slaps you on the right cheek, turn to them the other cheek also.
The Bible, Matthew 5:38-39
But I tell you, do not resist an evil person. If anyone slaps you on the right cheek, turn to them the other cheek also.
The Bible, Matthew 5:38-39
When starting your own company, it is easy to find competition everywhere. Every market map has a dozen logos on it. Every investor asks who else is doing this. Every product launch from a company vaguely near your space lands in your inbox like a threat. The fear runs so deep that many startups choose to go stealth, hiding their idea for months or years, convinced that the moment the world sees it, someone bigger will take it. I used to read those announcements with a tight chest, as if someone had just taken something from me. It took me embarrassingly long to realize that almost none of it mattered, and that the whole framing of “beating the competition” was quietly making me worse at building.
I am a software engineer, and I used to enjoy arguing with people for technical correctness. Code reviews, design meetings, mailing-list threads, dinner tables. If someone was wrong, I wanted them to know it, and I wanted them to know exactly why. I collected counterarguments the way I collected patches. I believed that if I just laid out the logic clearly enough, the other person would have no choice but to come around. Truth would win.
AI can now tell you whether code works. It reviews patches, spots bugs, suggests fixes, and explains trade-offs. Correctness is becoming cheap. Competence is being commoditized.
The evolution of eBPF (extended Berkeley Packet Filter) has been one of the most significant developments in Linux system observability and networking over the past decade. As we look at the landscape in early 2025, several key trends have emerged that showcase eBPF’s growing influence and future directions.
If you’ve been following the Linux kernel development community over the past few years, you might have noticed an interesting emerging trend in the field of memory persistence when using kexec to boot into a new kernel.
The Extended Berkeley Packet Filter (eBPF) has revolutionized how we extend and observe the Linux kernel. However, with great power comes great responsibility, and securing eBPF programs has been a persistent challenge in the Linux kernel community. Today, I want to share an innovative approach to eBPF program signing that addresses some fundamental challenges in this space.