[archarios]

I'd recommend not entirely dismissing web work as an option. If you do web work, there will be so many more jobs available to you. The work may not be as exciting in some cases. However, it is still good, well paying, work. The work may be less stimulating overall, but I think it's also less stressful. Which gives me more energy for other things in my life that I value more. There's more to life than work.

[hollerith]

>The work may be less stimulating overall, but I think it's also less stressful.

I cannot speak for the OP, but my hesitancy around front-end web work is that browsers seem like a mess, so I worry that my trying to build a reliable front end would tend to be too stimulating and too stressful for me.

[archarios]

Yeah that isn't completely false. However, frontend work is SO much better than it used to be. Having to support old versions of IE made everything suck for a while. We won't have to worry at all about IE at all soon: https://docs.microsoft.com/en-us/lifecycle/announcements/int.... That said, the testing story for frontend isn't as good as it could be. Cypress has gotten us really close to a place where frontend testing can have really good coverage. But it's not quite there yet IMO. All things considered, with a modern web stack, I think fullstack work is overall less stressful because web frameworks make it so you don't have to make big architecture decisions that you may deeply regret down the line. I do miss making those decisions because they are fun to think about, but having to make those decisions is a huge liability and source of stress IMO.