-"Instead of code and interfaces, we have processes and expectations. (By hiring career engineering managers, industry norms are imported. Firing a low performer may be a quick solution to a bigger underlying problem, deferred for the next manager.")
-This year, Meta laid off all their engineering managers that don’t code. It’s the same move that Google pulled 20 years ago, spawning Maps, Chrome and Gmail.
I've been noticing the similarities between how an organization is configured and a codebase. Upon reflecting why organizational change is hard, I made a comparison between the two and suggest an alternative.
2 points of brilliant insight:
-"Instead of code and interfaces, we have processes and expectations. (By hiring career engineering managers, industry norms are imported. Firing a low performer may be a quick solution to a bigger underlying problem, deferred for the next manager.")
-This year, Meta laid off all their engineering managers that don’t code. It’s the same move that Google pulled 20 years ago, spawning Maps, Chrome and Gmail.