This all sounds perfect! At {current_job} it feels like I'm slowly developing faux-ADHD from the "priority 1" task changing, often, multiple times a day. Perso

This all sounds perfect! At {current_job} it feels like I'm slowly developing faux-ADHD from the "priority 1" task changing, often, multiple times a day. Personal projects are a bit of a respite from it, since I get to focus on the one clear, long-term task for good stretches at a time, but recently I've been too burnt out to do even _more_ programming after yet another hectic day. I feel like I'm a competent SWE, but the nature of the work means everything is a ticking time bomb. If you're rushing all the time, code quality, testing, and all sorts of other sanity-restoring factors become a distant dream. I'd love to take ownership of a few aspect of a large system and slowly improve whatever I can. But the grass is always greener on the other side, so I'm sure this would come with plenty of negatives too. For one thing I feel like I'm too early into my career to be acting as a faux-CTO and being the go-to for all big tech decisions, infrastructure, etc, as well. Would you say there is an inflection point at which startups stop being like this? 20, 50, 100, 500 engineers? More? Sorry for the ramble!