Earlier quoted context omitted.
> "some of my old coworkers were shit and they deserve the shit-talk they get from me This is just such a red-flag in an interview. I have worked with some terrible people, for sure. But I would never talk about them in an interview. > t's only their own interpretation I chose a "cool" technology over the customer needs. Heh, I swear to god when I asked the question, "Why did you pick X technology?" they said, "Becau…
Now that you clarified, I actually think we're very much on the same page. ^_^ > This is just such a red-flag in an interview. I have worked with some terrible people, for sure. But I would never talk about them in an interview. Of course! Don't get me wrong. I am not making it a goal to shit-talk former coworkers in an interview. I try to avoid it, but what am I to do when I have to share that I maintained a Rails 4…
The reason I personally care about the skill of talking about bad coworkers tactfully is that I think it correlates with being able to navigate tricky workplace fuckups without making a big political mess that I have to clean up. The way I would phrase the above situation is:
"I inherited a Rails 4.0 app, and I wanted to upgrade it to Rails 4.1 so that we could take advantage of feature X. This wasn't on our roadmap, so I spent a lot of my own time looking into the feasibility and working on it in my personal time. However, it eventually became clear that too much of the legacy code would have to be totally redone, and there wasn't enough of a business upside."
> I am a firm believer of Einstein's saying "If you can't explain it to a 5-year old then you don't understand it"
Me too! Love this.