But you will also, in general, get better at solving simple problems, but those are not the problems you will be dealing with. To put it simply — The complexity of the issues will grow with your skill.

Absolutely and completely true. That feeling of "I have no idea how to solve this" never completely disappears because with more experience comes more expectations. People will come to you with requests for complex systems you've never even heard of, and you have to create a solution. But those problem solving skills you built on the path to senior really come in handy there, and then of course all the time-saving knowledge of knowing all the "gotchas" and what is plausible. Yes, I can easily solve most of the issues that juniors struggle with, but I still wrestle with my own issues semi-regularly.

Another thing people don't often talk about is skill atrophy. As your skill-set grows, the length of time between using skills becomes greater. Programming knowledge fades pretty rapidly. That's compounded by the fact that a decent chunk of your time is now supervisory. So you'll still spend lots of time in the docs, refreshing all that knowledge you worked so hard to acquire.

Really nice article, except for the work time section. Can we start to agree that overtime should not be normal? (To be fair, I don’t work in an industry with actual emergencies. There’s always tomorrow or next week. So maybe I’m missing perspective here.)

Well that, and the being laid off. At my (unionized, European) company it’s usually the longer you’ve been with the company, the more secure your job is.

I don't think anybody ever believed any of those things.

I hate popovers. This one not only covers the whole screen, it opens the virtual keyboard because of auto focus. So people actually subscribe like that? I don't. I leave.

This is a fantastic article. As a junior dev myself, I find that I share some of these misconceptions about our Senior Devs (who seemingly know everything when I ask them a question haha). Thanks for posting.