[sho_hn]

I have one of those jobs, and I don't contribute a lot of code at work anymore (sometimes, when it makes a difference or I can help save a lot of time).

I still write code almost daily however, e.g. for personal projects or in FOSS. For one, I love it as an activity - writing code is stress-relief for me. If I don't do it for some time I really feel deprived. I also think it's necessary to keep the first-hand knowledge of stacks and tools alive and well, e.g. for effectively communicating with engineers in a way both sides will enjoy.

I also do still make a point to e.g. do a MR regularly at work, partly to make sure I know the processes and their pain points, also so I can use my clout to complain if we make engineers waste time with stupid stuff, as processes also tend to accumulate cruft over time.

And obviously I don't think of writing code as a "lowly activity". Quality and skill matter on every level.

For that matter, you can also encounter quite a lot of "the architects don't know how to code"* stereotypes, so the subtle-disdain thing can go both ways (your comment may be exemplary). I try to prove them wrong by having written more and more different stuff than most :-)

* = https://i.programmerhumor.io/2021/11/programmerhumor-io-prog...