News for hackers. Stuff that matters.
Re:A CTO should be technical by pvorb on Monday September 26, 2022 @05:19PM (#32988590)
> Should they be able to jump into the code, start grabbing JIRA tickets on a moment's notice, or throw together a new feature when a deadline is looming? Absolutely not.

The point was that a CTO should be able to do this in theory. Of course they won't ever actually do this unless there's no other way.

If your CTO can actually relate to the problems of their staff, they'll be able to make better decisions which also see more acceptance.

Re:A CTO should be technical by scarface74 on Monday September 26, 2022 @05:43PM (#32988928)
I’ve had two jobs where I reported directly to the CTO - the first as Dev lead with people management responsibilities and the second as the de facto “cloud architect” that was responsible for the “application modernization” initiatives.

My second CTO was very technical and up to date the first wasn’t. The only difference between the two day to day was with the second one, I could use terms without defining them first. They both deferred to my technical judgement and I worked with the understanding of how to align my initiatives with the company’s.

I work with CxOs all the time in consulting now. I have no problem getting my ideas through CxOs or architecture review boards.

Re:A CTO should be technical by nordsieck on Monday September 26, 2022 @05:52PM (#32989038)
> My second CTO was very technical an up to date the first wasn’t. The only difference between the two day to day was with the second one , I could use terms without defining them first. They both deferred to my technical judgement and I worked with the understanding of how to align my initiatives with the company’s.

> I work with CxOs all the time in consulting now. I have no problem getting my ideas through CxOs or architecture review boards.

Something to consider: there is probably not much difference between technical and non-technical when their reports are good.

But a technical CTO can stand up to reports that want to go down an obviously bad road, whereas a non-technical CTO would have as much defense as I would at jiffy lube when the tech asks me if I want my fluids flushed. It kind of sounds like a scam, but I really don't know.

Re:A CTO should be technical by marcinzm on Tuesday September 27, 2022 @06:34AM (#32993580)
>But a technical CTO can stand up to reports that want to go down an obviously bad road, whereas a non-technical CTO would have as much defense as I would at jiffy lube when the tech asks me if I want my fluids flushed. It kind of sounds like a scam, but I really don't know.

The non-technical CTOs "defense" is having found which reports they can trust and support to make the correct tradeoffs. Then they do that. More broadly if your reports aren't competent or trusted enough to make the right decisions then find new reports.

The job of the CTO isn't to argue some stupid architectural point with people for hours. It's also not to blindly overrule them. Their job is to hire people that know more than them and can be trusted. Then it's to setup the processes within which those people can thrive.

In fact the problem with technical CTOs is that they can rely too much on their own technical knowledge versus fixing the damn organization. It's basically a bunch of band aids being put on a gushing wound.

Re:A CTO should be technical by geertj on Monday September 26, 2022 @07:09PM (#32989815)
> But a technical CTO can stand up to reports that want to go down an obviously bad road, whereas a non-technical CTO would have as much defense as I would at jiffy lube when the tech asks me if I want my fluids flushed. It kind of sounds like a scam, but I really don't know.

Very true. GP probably had good tech judgement which is why their technical CTO was following their judgement.

Re:A CTO should be technical by scarface74 on Monday September 26, 2022 @07:51PM (#32990139)
I had never logged into AWS when I was hired. I just had theoretical knowledge. In the land of the blind, the one eyed man is king, I’m amazed to this day that the CTO trusted me knowing that in advance. Don’t get me wrong, he didn’t blindly trust me. He pushed me harder than any other manager ever had to do things correctly and to think deeply and to write well reasoned documentation and presentations.

I told myself that there were only two positions at two companies that could have convinced me to leave. I got hired by one of those companies. He left less than a year later after the company was acquired for 10x revenue. He’s working somewhere else now. I would work for him again in a heartbeat if I were working anywhere else besides where I work now.

Re:A CTO should be technical by dijksterhuis on Monday September 26, 2022 @10:07PM (#32990896)
> whereas a non-technical CTO would have as much defense as I would at jiffy lube when the tech asks me if I want my fluids flushed. It kind of sounds like a scam, but I really don't know.

I am genuinely wondering if I need some jiffy lube for flushing those fluids of mine.

It... sounds like... a thing... that people... do?

Re:A CTO should be technical by pvorb on Monday September 26, 2022 @05:50PM (#32989011)
Thanks for the insight.

I'm wondering what the devs at both companies were thinking about their CTOs. My point wasn't that much about direct reports to the CTO, who might already be used to talking in management terms, but rather the developers who are directly affected by the CTO's decisions.

Re:A CTO should be technical by scarface74 on Monday September 26, 2022 @05:56PM (#32989077)
If the devs are reporting directly to the CTO, the CTO should be technical. If not, the CTO should delegate dev leadership to someone who is both technical and business oriented.

As my last company grew, the CTO just didn’t have the bandwidth to be technical at work and delegated different responsibilities to the people who could wear both the technical hat and had the soft skills needed. He would just dabble in things on the weekend. His entire family was technical. His wife was a lead data analyst for a telecom and his daughter got an internship as an SWE at BigTech.

Re:A CTO should be technical by tluyben2 on Monday September 26, 2022 @09:08PM (#32990601)
You are right; you have to relate to the problems to value your people more I find. I used to jump into code as cto and I lost good people because of it as they felt it was lack of trust (it was I think but I did not realise that back then). When understanding how things work and giving the team the means to get it done by supporting them instead of trying to do their job is something I see go wrong in many cto’s, including my former self. I still like coding more than managing but I realise that there are other people so much better at the code part and I need to hire and guide them.