4 ms·

The crazy thing I was hired because they allegedly wanted me to give opinions based on my experience. Like, they sense they're doing something wrong. But when I

The crazy thing I was hired because they allegedly wanted me to give opinions based on my experience. Like, they sense they're doing something wrong. But when I got here, it became obvious that no constructive criticism is really allowed. There are a couple of voices that dominate all conversation (team leaders) and they always win. I don't know what to do about it though.

Gibbon1 6y ago
The question I have isn't about programming then. It's who is you patron in this company? Also the reason the front end guys don't want you around is they know or some of them know their code is a steaming pile.
- potta_coffee 6y ago
  That's a good question. I'm not sure I have a patron but I'll have to think about it more. Your second point could be true.
  - Gibbon1 6y ago
    Sadly it might be this job is both not for you and isn't set up to be effective. The person to fix this needs to be a team lead and aggressive.
joshxyz 6y ago
Fair point. But another angle is in order for you to introduce some architectural changes, it better translate to improvements in the business-side metrics, which on most cases in hard to quantify beforehand, which leaves you into babystepping it as your only option. In your shoes maybe i'd also see it as a challenge in my own soft skills. At the end of the day it's also about selling them that your idea has some potential.
- potta_coffee 6y ago
  I'm aware that most of our technical issues can't be fixed without a lot of refactoring / rewriting at this point, but I see our real issues to be "people problems" rather than technology problems. Your comment gives me something to think about though, thanks.
  - AnimalMuppet 6y ago
    And it sounds like the "people problems" don't want to be exposed as the problem. So they're trying to make it look like you are the problem. From what you've said, the code objectively stinks, and the people are objectively unprofessional in problematic ways. You may not be able to fix it without getting rid of the team leaders. If you don't have either the authority to do that or the political pull to make it happen, then your best option is probably to run away.

Gibbon1 6y ago

The question I have isn't about programming then. It's who is you patron in this company? Also the reason the front end guys don't want you around is they know or some of them know their code is a steaming pile.

potta_coffee 6y ago
That's a good question. I'm not sure I have a patron but I'll have to think about it more. Your second point could be true.
- Gibbon1 6y ago
  Sadly it might be this job is both not for you and isn't set up to be effective. The person to fix this needs to be a team lead and aggressive.

joshxyz 6y ago

Fair point. But another angle is in order for you to introduce some architectural changes, it better translate to improvements in the business-side metrics, which on most cases in hard to quantify beforehand, which leaves you into babystepping it as your only option. In your shoes maybe i'd also see it as a challenge in my own soft skills. At the end of the day it's also about selling them that your idea has some potential.

potta_coffee 6y ago
I'm aware that most of our technical issues can't be fixed without a lot of refactoring / rewriting at this point, but I see our real issues to be "people problems" rather than technology problems. Your comment gives me something to think about though, thanks.
- AnimalMuppet 6y ago
  And it sounds like the "people problems" don't want to be exposed as the problem. So they're trying to make it look like you are the problem. From what you've said, the code objectively stinks, and the people are objectively unprofessional in problematic ways. You may not be able to fix it without getting rid of the team leaders. If you don't have either the authority to do that or the political pull to make it happen, then your best option is probably to run away.