Don't let my blunt way of writing make you feel like it should have been easy to see or will be easy to overcome.

It sounds like you have been through the transition from a career rewarding complete knowledge and understanding to today... where a "complete understanding" and depth of knowledge is not possible in the same way.

Rolling releases, CI, and cloud dev cycles with dependencies have completely changed what is expected of you - it is OK not to know every edge case in most situations today. The answer is a google or prompt away if a problem appears.

This wasn't really true 18 years ago... even though it doesn't feel like tech has changed a ton, it has.

If you decide to keep doing a rotation of hats and languages, you have to become very comfortable with identifying the value you add as a person involved in the process, even when you don't have every answer in your head.

In other words, being able to pop in and out of various startups tells me you have the ability to learn quickly. Why not just truly sit back and ask yourself what you want? Even if it doesn't fit the HN front page expectations, doing what you want with a lucrative skillset is as close to a good work/life balance as I have ever found. Holler if you wanna talk more, but otherwise I hope others will chime in.