#future-of-work
Every post tagged "future-of-work".
57 posts · showing 21–30
-
Which Jobs Go First: A Framework Rather Than a List
Lists of at-risk occupations age badly because exposure operates on tasks, not titles. Four properties score any task — and two people with the same job can land on opposite sides.
-
The Career Risk of Being Excellent at the Thing Being Automated
The most exposed engineers are often the best ones — not despite the skill but because of what the skill is. And the feedback stays good right up until the market for it changes.
-
If There's a Bubble, What Survives the Pop?
Whether it's a bubble is unknowable from here. More useful: assuming a correction, which parts survive — and previous cycles have a consistent answer about what separates the two.
-
Juniors in an Agent World: The Path That Still Works
"Learn AI tools" is the most common advice and the wrong one — everyone has them. What addresses the actual hiring objection is different, and the path inside is narrower but shorter than it used to be.
-
Why Systems Thinking Is Appreciating in Value
"Systems thinking" is vague enough to dismiss until you name the mechanism: agents work locally, and cross-cutting consequences are structurally outside their context. That gap is a person's job.
-
Becoming the Person Who Decides What Gets Built
The most common career advice in this shift, with the instructions attached. The conversation isn't gated by title — it's under-resourced, and one specific move changes outcomes immediately.
-
Skills to Deepen and Skills to Stop Investing In
The divest list is harder to write than the invest list and more useful — because the default is to keep investing in what you're already good at, and that's often the exposed thing.
-
Staying Employable When Code Generation Is Nearly Free
"Develop judgment, move up the stack" is true and unactionable. Six specific moves instead — and the hedge and the bet turn out to be the same actions.
-
Model, Loop, Harness: Three Layers and Who Owns Each
Three layers, three change rates, three skill requirements. Conflating the loop and the harness is why loop bugs get fixed with prompt edits — and why domain experts can't fix domain problems.
-
Prompt Engineering Was the Beginning, Not the Skill
It got named as a discipline when the prompt was the entire interface. It's now one input among several — and if better prompts have stopped helping, five specific things are usually why.