By definition, if what you're doing is working, it's the right way. There's nobody higher up the chain to tell you otherwise.
If it's not hitting the goals you're setting for yourself, you'll need to determine if the goals are unrealistic or if the approach you're taking to reach them is unrealistic (as CTO, that's often more of the job than writing the actual code).
It's hard to be at the top; it often feels like "working without a net." I changed companies to avoid that feeling when I was younger, and it's possible that's the right move. But if you stick it out, I just want to share that "working without a net" feeling only diminishes if you build a net for yourself (in the form of process you can use to determine if anything is working).
By definition, if what you're doing is working, it's the right way. There's nobody higher up the chain to tell you otherwise.
If it's not hitting the goals you're setting for yourself, you'll need to determine if the goals are unrealistic or if the approach you're taking to reach them is unrealistic (as CTO, that's often more of the job than writing the actual code).
It's hard to be at the top; it often feels like "working without a net." I changed companies to avoid that feeling when I was younger, and it's possible that's the right move. But if you stick it out, I just want to share that "working without a net" feeling only diminishes if you build a net for yourself (in the form of process you can use to determine if anything is working).