|
|
|
|
|
by rboyd
2133 days ago
|
|
Step 1: Realize this says more about the team/org than it says about you. Don't internalize much of this. Recall some of the most difficult projects you've taken on successfully. If you have something to be proud of, remember that you actually are pretty talented. Step 2: Consider that there's a high probability that you were hired to clean up the mess. Maybe your teammates would like nothing more than for you to jump on the grenades so they can tackle the high-profile projects and get the promotions. In this context it probably starts to make more sense what's happening here. Giving negative feedback is a cheap and easy way for your teammates to signal to management what the ranking order is (especially if management is non-technical or too busy to look at the details). Step 3: Decide if it's worth staying. This could mean playing the long game. It could mean having a strategy to rep up with management behind the scenes. It could mean doing the hard work of shoveling in the trenches and playing code janitor to earn the respect. It could just mean collecting the paychecks and associating less of your identity with this job while you pursue hobbies, family, whatever else. Spend some time with your teammates on a social level and find some common ground. If you all like each other first it's easier to work together and harder to criticize. |
|
In fairness, if the new person is competent it's usually very clear early on, and they tend to move on to better things fairly quickly.