WhoKnows.
← All briefings
MONEYACTIONCAREERTECH 2 stories

Daily Briefing — May 13, 2026


01

The Rise of the Bullshittery

Hacker News →
Tech shifts + Career & skills

Something is breaking in how professional credibility actually works, and if you've spent any serious time on LinkedIn recently you've probably felt it too. The piece making rounds on Hacker News puts a name to the pattern: a slow, grinding shift in which the modern economy has stopped rewarding people who genuinely know what they're doing and started rewarding people who are really good at appearing like they do. Thought leaders who lead nothing. Founders building nothing durable. AI experts whose entire expertise is a ChatGPT subscription and a high tolerance for writing long posts about it.

The author borrows from philosopher Harry Frankfurt, who wrote a short essay called On Bullshit back in 1986. Frankfurt's core argument was that bullshit is actually more corrosive than lying, because the liar at least acknowledges that truth exists and is worth hiding. The bullshitter simply does not care either way. That distinction matters a lot when you're trying to figure out why certain colleagues keep getting promoted while doing very little that's real.

SO WHAT

If you're building real skills while the people around you are optimising for visibility over substance, you need to understand that gap before it starts costing you opportunities.


02

Why senior developers fail to communicate their expertise

Hacker News →
Career & skills

There is a specific kind of career trap that catches senior developers more than almost anyone else, and it has nothing to do with their technical ability. It goes like this: the more you actually know about a topic, the harder it becomes to talk about it clearly to people who know less. The article makes this point through a sharp little case study. When someone says "AI agents will replace developers," a non-developer hears a reasonable prediction about the future. A senior developer hears a technically illiterate statement that ignores system complexity, edge cases, maintenance debt, and about a dozen other things they deal with before lunch. Same words, completely different meaning, based entirely on what the listener already knows.

Here is the problem. If you are the senior developer in that scenario and you respond by explaining all those nuances in technical detail, you do not sound smart. You sound defensive and out of touch. The people who actually have less context walk away thinking you are protecting your turf rather than engaging honestly with the idea.

This is fundamentally a communication problem dressed up as a technical debate. And it is the kind of problem that quietly stalls careers, because leadership stops seeing you as someone who can translate expertise into direction. They start seeing you as someone who complicates things.

SO WHAT

If you cannot explain what you know to someone who does not share your context, your expertise becomes invisible to the people who decide your next role. Pick one technical opinion you hold strongly and write a two sentence version of it aimed at a non-technical manager, then check whether it still sounds like your actual position.