← Back to context

Comment by ozim

6 hours ago

Not the OP you asked but.

I think it is sour grapes that new CTO didn’t know shit and even did full embarrassment on display - yet tech guy who knew his job was let go most likely with his team just because CTO thought whatever they were doing should be in Java.

also a sense of broken promises to the CTOs fault

javascript coder joined taking the company's statement in good faith "everything will be javascript, the front and back end both" and happily did it

New CTO joins, warmly visits all, dude who joined in good faith parrots his understanding of what we're doing to the CTO. CTO reacts "NO IT MUST BE JAVA" and this is a flex new CTOs love to do -rewrite everything- often to failure

javascript coder now arguably may no longer be needed if he's not a java programmer, maybe CTO is bringing in their own guys, gets canned.. gets canned by a clown who (a) is watching porn during work and (b) shows it to everybody and (c) leadership above the CTO saw this and did nothing