> accomplishing things [I also ended up at a BigCo along with others from a small startup that pivoted multiple times after making v1 products that could have

> accomplishing things [I also ended up at a BigCo along with others from a small startup that pivoted multiple times after making v1 products that could have been successful.] What I learned is to reframe expectations. At the startup, I could develop software and features rapidly with no impediments than my own lack of knowledge in an area. At the BigCo, the product is large, changes are slow, and processes are safe. The payoff though is that when you do ship that feature, it's being used by thousands-to-millions more users than it would have been at the startup. At the same time, all the one-off things I used to do at the startup should have been streamlined at the BigCo so that I can think primarily about the problem I'm trying to solve and not the peripheral routine elements of every service that gets shipped. If this is not the case, perhaps the BigCo's processes are not very well streamlined. I've found some ways to adapt, but some things still take much longer than they should, like PR reviews (but I'm also guilty of being a slow reviewer). > emotionally exhausting This is because you have an expectation that a certain thing should only take a certain amount of time and effort. The best general advice is to work on multiple things concurrently, so that when one thing has delays you can switch to another one that's ready for work. You have to decide whether you want to actively improve these inefficient processes, accept them, adapt, or move on. Anything else will be suffering. If you move to another BigCo the annoyances will be different more to your liking, or not.