3 ms·

Your reply aptly explains why your peers aren't a fan of working with you. You sound like an a-hole. Even if you were the principal engineer of the entire org

Your reply aptly explains why your peers aren't a fan of working with you. You sound like an a-hole. Even if you were the principal engineer of the entire org and made dumb, rash decisions like this, I'd tell you to go pound sand irrespective of your seniority and title. So you're 4 months in, you made a hasty prod change on a database with very little oversight. That tells me you're neither senior nor someone who can work well with others. I'm not saying having 'strict' turned off was a good idea, but nobody working at your firm wants to deal with some new unexpected behavior over the weekend caused by some over zealous dev who made some change because he/she believed they were right.

celticmusic 7y ago
It's obvious that something about this is personal for you. You're making specific claims here that directly contradict what I've stated. I'd list them out, but really I don't want to waste my time on someone who is obviously angry about something unrelated.
flukus 7y ago
Where are you getting the idea that this was a dumb rash decision? It sounds like they upgraded the database instance without proper QA in the first place and that this created a lot of issues. OP didn't specify if this was their decision or not, but even if it was there might be some good reasons for it and many of those reasons point to further organisation incompetence. The only rash decision OP made (from the information available) was to disable the feature in production to at least get the appearance of everything working, which was the status quo. This is shooting the messenger, the product was silently failing for god knows how long and your blaming the person that forced the organisation to acknowledge those failures and their own personal incompetence. And they did this in a way that only had an immediate impact on non-production systems. I get the impressions you can't work well with others, because it requires a good dose of humility and the ability to acknowledge problems. Sweeping those problems under the carpet to bite people in mysterious ways at odd times is someone that's difficult to work with.
- celticmusic 7y ago
  Thank you for this response. What you've described is pretty much how I see it. And I'm not claiming that there weren't things I could have done better, I've thought about it and I definitely could have done things differently. But at the end of the day their response was a gross overreaction and was politically motivated. No one had any real problem with my decisions until that email chain.

celticmusic 7y ago

It's obvious that something about this is personal for you. You're making specific claims here that directly contradict what I've stated. I'd list them out, but really I don't want to waste my time on someone who is obviously angry about something unrelated.

flukus 7y ago

Where are you getting the idea that this was a dumb rash decision? It sounds like they upgraded the database instance without proper QA in the first place and that this created a lot of issues. OP didn't specify if this was their decision or not, but even if it was there might be some good reasons for it and many of those reasons point to further organisation incompetence. The only rash decision OP made (from the information available) was to disable the feature in production to at least get the appearance of everything working, which was the status quo. This is shooting the messenger, the product was silently failing for god knows how long and your blaming the person that forced the organisation to acknowledge those failures and their own personal incompetence. And they did this in a way that only had an immediate impact on non-production systems. I get the impressions you can't work well with others, because it requires a good dose of humility and the ability to acknowledge problems. Sweeping those problems under the carpet to bite people in mysterious ways at odd times is someone that's difficult to work with.

celticmusic 7y ago
Thank you for this response. What you've described is pretty much how I see it. And I'm not claiming that there weren't things I could have done better, I've thought about it and I definitely could have done things differently. But at the end of the day their response was a gross overreaction and was politically motivated. No one had any real problem with my decisions until that email chain.