4 ms·

"I am not happy" - Yes you should quit. Keep in mind this year has been incredibly unusual in terms of productivity. All the issues you describe are opportunit

by kanobo 6y ago

"I am not happy" - Yes you should quit. Keep in mind this year has been incredibly unusual in terms of productivity. All the issues you describe are opportunities to have huge impact on a global scale if you decide to solve any of them. But if you truly are disgusted by the state your company then that's not your path. I think you would likely thrive if you set your own path and work in an environment you built. You might need to quit once your creation becomes too successful though to avoid this problem again.

xiphias2 6y ago
There are literally thousands of teams in more than 50 cities in the world he can easily move to. Quitting so fast without evaluating his options would be a stupid decision.
- kanobo 6y ago
  The costs of doing business at that scale disgusts the engineer, that's not going to be different in another city. This engineer is likely intelligent and has been at the company for a year so I have no doubt he has considered other opportunities within this company so yes I do think he should quit as soon as he has a plan. Many people in this thread think the asker is somehow unintelligent and a slacker. I'm answering assuming this eng is smart and eager to work but has internal turmoil.
  - xiphias2 6y ago
    I was at a FAANG company as well (Google, with extremely slow dev tool velocity), and I don't think he isn't intelligent. But there are workarounds of the official dev process. I liked working on parts of search quality for example (or any data mining project), where most of the time (and the way to promotion) is spent on research, not software development. It means that 90% of the code we write don't have to be committed (code reviewed, tested, documented, going through the approval process), just the code that goes to production. The smartest colleague of mine spent a lot of time figuring out the root cause of data/search quality issues, and made the smallest possible change in the system to get his change through. It's an art in itself, and can make a lot of impact and lots of money to the company as well.

by kanobo 6y ago

xiphias2 6y ago

There are literally thousands of teams in more than 50 cities in the world he can easily move to. Quitting so fast without evaluating his options would be a stupid decision.

kanobo 6y ago
The costs of doing business at that scale disgusts the engineer, that's not going to be different in another city. This engineer is likely intelligent and has been at the company for a year so I have no doubt he has considered other opportunities within this company so yes I do think he should quit as soon as he has a plan. Many people in this thread think the asker is somehow unintelligent and a slacker. I'm answering assuming this eng is smart and eager to work but has internal turmoil.
- xiphias2 6y ago
  I was at a FAANG company as well (Google, with extremely slow dev tool velocity), and I don't think he isn't intelligent. But there are workarounds of the official dev process. I liked working on parts of search quality for example (or any data mining project), where most of the time (and the way to promotion) is spent on research, not software development. It means that 90% of the code we write don't have to be committed (code reviewed, tested, documented, going through the approval process), just the code that goes to production. The smartest colleague of mine spent a lot of time figuring out the root cause of data/search quality issues, and made the smallest possible change in the system to get his change through. It's an art in itself, and can make a lot of impact and lots of money to the company as well.