Ask HN: I don't enjoy being a CTO.  Now what?
What I&#x27;m about to say may be considered harsh, but I promise I don&#x27;t mean it to be.<p>Quit.  Just leave.  Go back to coding.  It&#x27;s obvious you don&#x27;t enjoy management, there&#x27;s no shame in admitting that.  Rather than inflict your misery on the rest of the team, get back to your wheelhouse where you can be happy, your team can be happy, and ultimately your company (current or future) can be happy.<p>I have worked in a job where the CTO (my boss) was in your exact position (in fact, if it weren&#x27;t for your style of writing - English was very obviously his third or fourth language - I would almost bet money that you were him, your stories are that eerily similar) and it was a <i>miserable</i> experience.  $CTO was an otherwise brilliant coder who was on his first cto-gig outside of &#x27;team leader&#x27;.  Outside of work, he was a great guy - warm, personable, funny.  At work, he resented not being able to code in many different ways, often with the team bearing the brunt of his misery. He&#x27;d often make decisions for others to implement, then second (or third) guess himself days or weeks later, insist we throw out all the work, and start again.  He&#x27;d often be irritable, make rash decisions, have temper flare-ups, ask for feedback then get upset when he got it, etc.  It was a bad scene for all involved, but the dude was a walking personification of the Peter Principle.  He would have been infinitely happier remaining a coder, and his team (myself included) would have been infinitely happier with a CTO comfortable in a leadership position.