{"id":9020,"date":"2025-10-11T08:42:40","date_gmt":"2025-10-11T08:42:40","guid":{"rendered":"https:\/\/pokecon.jp\/job\/?p=9020"},"modified":"2025-10-11T08:42:40","modified_gmt":"2025-10-11T08:42:40","slug":"the-illegible-nature-of-software-development-talent-surfing-complexity","status":"publish","type":"post","link":"https:\/\/pokecon.jp\/job\/9020\/","title":{"rendered":"The illegible nature of software development talent \u2013 Surfing Complexity"},"content":{"rendered":"\n<\/p>\n
\n

Here\u2019s another blog post on gathering some common threads from reading recent posts. Today\u2019s topic is about the unassuming nature of talented software engineers.<\/p>\n

The first thread was a tweet by Mitchell Hashimoto<\/a> about how his best former colleagues are ones where you would have no signal about their skills based on their online activities or their working hours.<\/p>\n

\n
\n
\n
\n

One of the most impressive people I’ve ever worked with was a guy who spent a decade prior working on the same team at the same company iterating on a kernel driver for a single specific network card. He clocked in at 9 and out at 5. Predictable promotions. Nothing crazy.<\/p>\n

During\u2026<\/p>\n

\u2014 Mitchell Hashimoto (@mitchellh) September 16, 2025<\/a><\/p><\/blockquote>\n<\/div>\n<\/div>\n<\/figure>\n

The second thread was a blog post written a week later by Nikunj Kothari titled The Quiet Ones: Working within the seams<\/a>. In this post, Kothari wasn\u2019t writing about a specific engineer per se, but rather a type of engineer, one whose contributions aren\u2019t captured by the organization\u2019s performance rubric (emphasis mine):<\/p>\n

\n

They don\u2019t hit your L5 requirements because they\u2019re doing L3 and L7 work simultaneously. Fixing the deploy pipeline while mentoring juniors. Answering customer emails while rebuilding core systems. They can\u2019t be ranked because they do what nobody thought to measure.<\/strong><\/p>\n<\/blockquote>\n

The third thread was a LinkedIn post written yesterday by Gergly Orosz<\/a> (emphasis mine).<\/p>\n

\n

One of the best staff-level engineers I worked with is on the market.
\u2026
What you need to know about this person: every team he\u2019s ever worked on, he did standout work, in every situation. He got stuff done with high quality, helped others, is not argumentative but is firm in holding up common sense and practicality, and is very curious and humble to top all of this off.
\u2026
And still, from the outside, this engineer is near completely invisible.<\/strong><\/p>\n

He has no social media footprint. His LinkedIn lists his companies he worked at, and nothing else: no technologies, no projects, nothing. His GitHub is empty for the last 5 years, and has perhaps a dozen commits throughout the last 10.<\/p>\n<\/blockquote>\n

That reason that Mitchell Hashimoto, NIkunj Kothari, and Gergly Orosz were able to identify these talented colleagues as because they worked directly with them. People making hiring decisions don\u2019t have that luxury. For promotions, there are organizational constraints that push organizations to define a formal process with explicit criteria.<\/p>\n

For both hiring and promotion, decision-makers have a legibility<\/a> problem. This problem will inevitability lead to a focus on details that are easier to observe directly precisely because they are easier to observe directly<\/em>. This is how fields like graphology<\/a> <\/em>and phrenology<\/a><\/em> come about. But just because we can directly observe someone\u2019s handwriting or the shapes of the bumps on their head doesn\u2019t mean that those are effective techniques for learning something about that person\u2019s personality. <\/p>\n

I think it\u2019s unlikely the industry will get much better at identifying and evaluating candidates anytime soon. And so I\u2019m sure we\u2019ll continue to see posts about the importance of your LinkedIn profile, or your GitHub, or your passion project<\/a>. But you neglect at your peril the engineers who are working nine-to-five days at boring companies.<\/p>\n<\/p><\/div>\n