3 ms·
One time I got the CTO fired because I exposed the fact that he literally didn't know how to use a computer. To be fair, he had other issues as well. But they h
by latchkey 5y ago
One time I got the CTO fired because I exposed the fact that he literally didn't know how to use a computer. To be fair, he had other issues as well. But they hired some big exec from Yahoo and never asked him anything during the interview. He was there in name only.
The actual CTO was my boss and definitely a strong coder but was deathly afraid of Java annotations for some reason. It was too "black magic" for him as he preferred to define all his Spring stuff in pages of XML and log into the servers directly to edit code in production. He also had anger issues and once slammed his fist into a metal cabinet, verbally assaulted employees and flirted with all the interns (despite being married with a kid).
The view from the office in downtown SF was excellent and I think that you should write code to be a CTO. The job isn't just about managing people. It is about having product vision. You're not going to develop as good of products if you haven't done it before yourself. Sure, there might be a few super stars out there who can do all this anyway... but that's why they are stars...
Keep it weird though.
- jjtheblunt 5y agoHe disliked annotations but used Spring? Is that not ironic?
- wiradikusuma 5y agoSpring started with XML.