3 ms·

He seems to be a good coder with poor judgment. But I think it would be wiser to manage him better than to fire him so long as he recognizes what he did was wro

• Stevvo 4mo ago
  He doesn't recognize it. He claims in the post he was fired because certain leaders were afraid of being disrupted.
  • pydry 4mo ago
    This seems pretty plausible. This tool probably did threaten some product line or other with cannibalisation.
    • IncreasePosts 4mo ago
      Is it plausible? Imagine any leader that is not sundar trying to get this person fired. At some point, that leader would need to justify to either their leader, or a similarly leveled peer why they budgeted x SWE-years(where x is probably > 25) for a project that took this person far less than 1 SWE-year.
      • wiseowise 4mo ago
        You’d be surprised how petty some people are.
      • itemize123 4mo ago
        sounds even more plausible under that scenario?
      • zipy124 4mo ago
        It's pretty easy to justify that sort of thing off the notion that doing something "properly" requires more man hours. There are truths to both sides of the argument.
    • sleepybrett 4mo ago
      it makes them look lazy for not doing it already, this tool was sorely needed.
• jofzar 4mo ago
  My bet is that he was reprimanded for this and then didn't back down, hes even in the comments here now arguing about it
  • xnx 4mo ago
    Bingo. There's lack of detail about the original circumstances, but behavior since points to what the problem was. A lot of times you start the discipline process for a rogue employee and then become even more certain about the decision.
• jxyxfinite 4mo ago
  I suspect he ported over/heavily referenced how the official cli worked and got into massive legal trouble by open sourcing it. It’s hard to grok that someone would go to extensive length to get him fired without seriously violating company policy