being a senior dev is boring. whatever you try, works -_- whatever problem you face in a new tech, gets fixed within a few minutes -_- old problem solutions are either in a repository you remember or in a browser bookmark -_- juniors come to you for solutions instead of googling -_-
there is absolutely no excitement in work life -_- dont be a senior dev -_-

Nah it isn't that bad - give it a try.

@iiii Lulz, but yeah, i used "explaining stuff" as a means of procrastination too...

Being ”senior” still does not take away imposter syndrome. That’s a wisdom aquired that we need to teach much more. We need to solve problems together without discussing ”senior” or ”junior”.

ALIGNING stuff, i.e. tech stack used (current and future), ways of working, measuring stuff (measure everything tech but the team (soft values, HUMANS!) should only have a communicated vision).

I think seniority should give you mandate to bring happiness to your team (which leads to value if a good enough path has been selected). Seniority should also slow things down and assert that the foundations of quality software engineering has been met. I did a system review where I glanced at the code base and forced the developers to some simple abstractions and unit testing. They (juniors) told me before that automated testing was implemented which was a lie.

As a senior, I think you have to start leading. You need to think differently about your role. If you got no mandate, leave.