In 2017, I found myself stepping into the shoes of a CTO for the first time. I joined a small startup as a senior developer, and before I knew it, I was
Don’t know why but for some reasons I cannot take people seriously that write articles about the importance of their role.
In the media, CTOs are often portrayed as tech geniuses or wizards, single-handedly coding complex algorithms or inventing groundbreaking technologies.
Not sure what kind of media the author of this articles (op?) consumes, but I don’t know anybody who thinks something like that.
That first paragraph is basically my job now, except for the investors and clients part. We have an actual CTO so he gets to deal with all that crap and I can focus on the tech stuff.
He also talks to investors and clients, but about business focused subjects vs tech focused subjects. Beyond that I’m fairly vague on what he does but I’m happy with that because it means I can keep my focus (mostly) on what I find interesting.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
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
Don’t know why but for some reasons I cannot take people seriously that write articles about the importance of their role.
Not sure what kind of media the author of this articles (op?) consumes, but I don’t know anybody who thinks something like that.
Definitely hyperbole, but it’s not uncommon for CTOs to be the main author of a company’s tech.
Somehow I get the sense that humility and authenticity aren’t required skills
Those aren’t required for the rest of the C Suite, why would CTO be different?
That first paragraph is basically my job now, except for the investors and clients part. We have an actual CTO so he gets to deal with all that crap and I can focus on the tech stuff.
What does the CEO do?
He also talks to investors and clients, but about business focused subjects vs tech focused subjects. Beyond that I’m fairly vague on what he does but I’m happy with that because it means I can keep my focus (mostly) on what I find interesting.
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.
Apparently “concise writing” is not one of the core skills.