i just read this post from tef & it's correct, i have enough experience to nod along with it, but mainly what it makes me aware of is how anomalously much of my career has been writing code on a team where i was the only one writing code. which doesn't mean that i've never done it, or that i think i'm especially bad at it - but that i read this post and what it mainly illuminates is the attitudes it is pushing back against & the frustrations in terms of practices that those attitudes lead to.
and i guess what makes this feel especially strange is that i have a lot of the component pieces of the skillset of a senior engineer. i've had a lead role, i've mentored people, i've built systems and then maintained them for years, i've built systems that other people have maintained for years while periodically asking them how it's going and if they wish i'd done anything differently, i've definitely had many jobs where a primary thing i did was assess novel technologies and see whether they would make sense as a thing for us to use (generally: no), i've had jobs where i talk to programmers and ask them how much work a thing would be to do, and then had to decide whether to push back on their answers based on my own knowledge of the system and the problem (in both directions, actually)... but i've rarely actually written code on a project alongside other people who are also writing code, and so i am aware there are these normal frustrations that have built up in others' bones and that i just don't feel.