[unrestifarian]

I have felt and feel a lot of what you are saying. Realizations I've made:

1) Constant change is a huge part of the software industry - we have to accept it, or become a craftsman focused on potentially moribund tech, or get out (and do construction or become a career less prone to change). I'm in favor of the latter two as I don't want to constantly be learning new tech that I don't like.

2) Not all new tech is good. So much of tech is the result young kids re-writing a solution that already exists. A lot of the times the new solution is worse or not any better than what exists. Occasionally it's better - but I think that's rare. I see it as a law of nature - the kids want ownership and maybe they're right that something about the old way of doing things is bad or cumbersome - thus new tech is born (even if not terribly better than what had existed).

3) AWS has been around forever - my company has been using it for over a decade now, so I don't think of it as novel or new. Yes, it's a pain in the arse in some ways, yes it's clunky, yes IAM sucks to configure - but it does have its advantages - scaling/replicatability. I suggest making friends with it, OR committing to not 'doing devops' or being 'full-stack' and being OK with that. It's not going away!

Most important message: - focus on tech you enjoy (however narrow or broad) - because that's what will keep you passionate - and most likely will lead you to being good at it (and thus employable).