There is an incredible danger with increasing seniority that you deal entirely in abstractions and don’t build things. Or worse—you think that building things is for juniors.

🚩 You build the platform but nothing on the platform.

🚩 You build the framework but nothing with the framework.

🚩 You devrel but it becomes 100% rel and 0% dev.

Don’t fall into this trap! Be your own customer—keep building 🏆

this toot has incredible but accidental “hair club for men” marketing energy
@zachleat this is not just a programming problem
@zachleat i might be a weirdo but i came up thinking seniority (of position, not time) correlated with skill
@exchgr seniority is only a measure of power 😅
@zachleat my puny junior mind was blown when i first fully internalized this lol
@zachleat @exchgr for a lot of folks at my last gig, it was literally just how long you'd been there, regardless of your (lack of) output or progress
@haliphax @zachleat a recipe for success if i ever saw one!
@zachleat … reminds me of application frameworks developed by systems programmers who don’t really have application development experience.

@zachleat agreed, though there’s a corollary risk I’ve seen with leads who go super deep building a tool for their own purposes, then lambast folks who have trouble using it in a different context as “holding it wrong”

“Architecture astronauts” are bad, but beware of “Titan Submersible devs” as well

@zachleat

don’t build thingsWEN?

25 years I've ben building things! When do
I get to build the abstractions!?

@zachleat “engineering manager” without engineering
@zachleat This is a common problem in professions, which Andrew Abbott calls "Professional Regression" aka.: Prestige being given to "pure" forms of activity that do not deal with the core tasks – which, solving problems of people-not-from-the-profession, are professionally impure and messy.