Live data from Hacker News

A CTO should be technical

blog.southparkcommons.com

211–220 of 367 posts

Re: A CTO should be technical

#211
post #185
post #177

Earlier quoted context omitted.

I hope that's what the original poster who you quoted meant, because I don't see all that much wrong with the examples you mention. No, there's no need to engage people in discussions about things if it doesn't really impact them, or they can't really jump in and help the situation. However, in the absence of some legal requirement to keep quiet, if some employee got wind of one of those situations, and came to you a…

Yeah for sure completely agree. Tbh I didn't think too deeply about the scenarios, they were more to put context around what I meant by "fires", and how not mentioning them (which some might consider lying) is necessary sometimes to steady the ship (though if a team member asked I'd let them know what's happening). I do think scenario #1 is interesting to talk about though. I.e. If I was that manager receiving that n…

I would add including the team once the path is clear.

What scares people is uncertainty. Not uncertainty of outcome (50% chance this will save us). It's uncertainty of what the options are, what the roadmap might be. That's the job of a good manager. Insulate the team from uncertainty and politics. Figure out the space of options, what the outcomes can be, negotiate it with leadership, and present a reasonable and clear plan to the team. That won't cause panic.

Show the team the plan, its rationale, and what needs to be done. What the upside will be. Let them take ownership of it. Let them make the lower-level decisions of how to split time, of what to prioritize, of what edges can be cut. With your feedback.

People generally don't bail when faced with a challenge. They like challenges. You just need to define the challenge clearly and set the path for overcoming it.

Re: A CTO should be technical

#212
post #201

> So let me put it plainly: the CTO/VPE/Engineering Director candidate should pass your coding interview. In fact, they should excel. I've interviewed over 300+ CTOs over the last 8 years. I don't think the author is saying this literally, but i'll bite - no the CTO doesn't need to pass your coding interview. CTOs need two capabilities to excel - technical ones and human resources ones. That's it. No need to get any…

If the CTO isn't a technical domain expert then they are just middle management overhead.

Re: A CTO should be technical

#213
post #142

Earlier quoted context omitted.

> You are espousing false virtue/armchair quarterback. Real life is complex and lying can save many people jobs. I'd rather my job disappear than still be there because someone with employment power over me lied to me. This isn't false virtue or armchair anything. No exceptions, or I don't work with you ever again. It's not hard. Learn to communicate effectively, and learn to treat your employees with the respect the…

Consider that you're advertising yourself as the type of person who absolutely must be lied to in order to maintain morale. I've been close to situations where the ICs did their absolute best and it was a total waste because of politics outside of their control. Do you tell them that so-and-so highly-respected person was shit-talking them because of an unrelated agenda and invalidated all of their work? Or do you tel…

> Or do you tell them good job (it was a good job) and not get into it?

Personally, I’m okay with not being informed about everything that’s going on. I work at a big enough company that I couldn’t possibly know what goes on all the way up the management chain, but even if I worked at a small startup, I could understand if management didn’t want to be fully transparent. I don’t need to know; it’s none of my business. But I won’t stand being lied to – even about small things, or things I don’t even care about in their own right. I see lies as a breach of trust and as a sign that I can’t trust that person, moving forward.

So it depends on what you mean by “not get into it”. If you really stick to truthful statements, and if there isn’t a high enough prior expectation of transparency to make it amount to a lie of omission, then leaving it at “good job” is perfectly fine. But if you do lie… well, if I find out, I’m probably leaving.

Re: A CTO should be technical

#214
post #213

Earlier quoted context omitted.

Consider that you're advertising yourself as the type of person who absolutely must be lied to in order to maintain morale. I've been close to situations where the ICs did their absolute best and it was a total waste because of politics outside of their control. Do you tell them that so-and-so highly-respected person was shit-talking them because of an unrelated agenda and invalidated all of their work? Or do you tel…

> Or do you tell them good job (it was a good job) and not get into it? Personally, I’m okay with not being informed about everything that’s going on. I work at a big enough company that I couldn’t possibly know what goes on all the way up the management chain, but even if I worked at a small startup, I could understand if management didn’t want to be fully transparent. I don’t need to know; it’s none of my business.…

[deleted]

Re: A CTO should be technical

#215

Earlier quoted context omitted.

> This will 100% require lying or being non-transparent at some point. Are you ok with employees and reports reciprocating by lying to you as well.

Yes. FYI They will lie to you regardless.

> Yes. FYI They will lie to you regardless.

If you create a culture where you lie, then people will lie to you.

If you create a culture where you are honest, people will be honest back to you.

There's nothing more powerful than going to your team and saying "Look, I fucked this up. I need your help". Honesty is disarming.

I'm in a field where I manage scientists. If people start to lie to me or even start to bend the truth a little, we will waste years chasing ghosts. The people that work for me are very savvy at figuring out what I think might be true and they can always present just the right data to make me happy. I had to learn early on that I need to be really explicit: we need to do good work, it doesn't matter if I'm right or wrong, it doesn't matter if they're right or wrong, all that matters is progress.

So no. Your employees don't need to lie to you. Mine come to me regularly and explain what went wrong. Judgement-free. And we do deep dives to prevent problems in the future.

You are causing the problems, not them.

Re: A CTO should be technical

#216
post #23

I just became a CTO. So, let me bear my thoughts. Since July of this year I've been CTO for a small games company, I've worked in this industry before in a more specialised role but this is much broader scope. I've gone from being responsible for 1 person to 10 which will likely become 50 by the end of next year. I'm terrified. I'm terrified because I feel like I will let my reports down. I'm terrified because a lot…

Sounds like you are making the technical to leadership transition extremely quickly. I think you will find that it’s the speed of that transition, rather than the transition itself, that is giving you difficulty.

One thing that has helped me, and may be helpful to you as well, is to look at your new role as an engineering problem. Logistics and process may not feel technical but they 100% are, and if you approach them with the same problem solving mindset and intellectual curiosity as, say, a coding task, you will enjoy them a lot more, and may even find that you become very successful at them.

Re: A CTO should be technical

#217
post #94

Earlier quoted context omitted.

Curious to know where the statement "real life is not fair" is coming from / what it's referring to.

> do you want an opaque company where politics drive individual success >you want a transparent company where employees respect their leaders and where the best insight wins? The comment I replied to has very startup company silicon valley skew to it naive of the majority of the world. Very few of us are in any position to determine or change the political/cultural/driving forces of a company we have to work at. Usua…

Yet in some companies, the CTO has the ear of the top executives. If some scheming non-technical career climber can get their way into the CTO's position, they can get to the top of the tree.

A lot can be achieved by aligning themselves with successful projects and crapping on others at the start or just at the cusp point of success or failure.

Re: A CTO should be technical

#218
post #210

The CTO should be able to liaise with employees, customers, and upper core management. While some technical understanding is needed to contextualize operational costs, it is hardly a primary skill requirement. Some may find it convenient to overburden employees with 6 roles in a small firm, it is often not a wise decision. Ignoring burnout factors, a company could end up with a very cool looking toy infrastructure, t…

That would be a Chief Liaise Officer.

You obliviously haven't met a CTO at an 8000 user facility.

Damage control is the primary Role... whether you want the task or not.

Most lack the discipline to tolerate that level of verbal abuse. ;)

Re: A CTO should be technical

#219
post #23

I just became a CTO. So, let me bear my thoughts. Since July of this year I've been CTO for a small games company, I've worked in this industry before in a more specialised role but this is much broader scope. I've gone from being responsible for 1 person to 10 which will likely become 50 by the end of next year. I'm terrified. I'm terrified because I feel like I will let my reports down. I'm terrified because a lot…

I've reported directly to good CTOs and really bad ones. The shitty ones: - Either never built trust or broke trust. - Were impulsive and reactionary. - Didn't rely on the expertise and skills of their reports as much as they told them what to do because they already knew everything. Didn't ask questions. Gave orders. - Literally used the words, "because I said so". - Believed that they were the only one doing any re…

[deleted]

Re: A CTO should be technical

#220

This really is a one-sided view. I'm not saying it is an incorrect view, but I find that all dogmatic stances are only correct part of the time. Some small companies need a technical CTO. Large companies need a leader who can effectively delegate the technical aspects to his organization. Companies in the middle... will vary.

If the CTO isn't technical, how do they know what to delegate? Who to delegate to? How do they determine who to listen to?
Post reply on HN