Not sure if this counts, but I went from software engineering to embedded systems. Here's how I feel it's different:

- The space evolves at a slower pace than regular "software", so I'm less stressed about keeping up with the latest/greatest;

- Resources are more constrained so there are less whacky design patterns and architecture - just simple code;

- Longer development lifecycle (due to hardware), so less being rushed to ship half-assed features.

There are downsides, too:

- Less cool algorithms (and language features), more shunting around data and debugging;

- Not as well-compensated, but still pretty good;

- Hard to be 100% remote, since you often need access to hardware.

Obviously, my experience is not universal, just my sample of n=1!

I got completely burnt out programming, so I quit and built a house on a rural block of land. You need to like being outdoors, even when the weather is miserable. The biggest issue is building up your savings in advance and being comfortable living on a lesser income.

Many former colleagues that I have kept in touch with won't give up their lifestyles which they can only afford because of their above average income. Being frugal and happy doesn't suit most folks.

There is also the possibility to optimise for free time.

- Get a remote job

- only work four days. Look for one with very little meetings.

- do your real work 4-5 hours a day, go for a walk, a run, whatever during working hours

Show me another job where I can make 100k basically working 16-20 hours a week.

Has anyone found another job that pays so well for so little, yet? Anything I found is a significant pay cut or significantly harder and more stressful work, so I'm still programming.

I really love technical sales. Management wasn't for me (hate meetings), and I get paid more.