this post was submitted on 22 Jul 2023
21 points (78.4% liked)
Programming
17489 readers
66 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is a bit of a narrow view of a very vague term. Having worked with many different sizes of organisations i can say that the responsibilities of whomever is labelled CTO are completely arbitrary. The only thing you can establish is that they are the person accountable for the technology decisions.
Sometimes that's a legacy developer, sometimes that's the first sys-admin.
Sometimes it's the VP of engineering.
Sometimes that's the person that maintains the best relationships with software vendors.
Sometimes it's the person that was hired externally to explain the tech to the CEO and let's them make informed executive decisions.
Sometimes it's just a public figure used to promote the org and maybe do DevRel.
Sometimes it's the Architect that designed the ecosystem.
Sometimes it's the ancient programmer that has kidnapped the entire codebase so that no-one else can sanely work on it.
Sometimes it's a six sigma type that setup the ticketing system, PRs and the release process.
At any size, the CTO is whatever the org needs him to be at that point.