Live data from Hacker News

Soft Skills in Engineering Leadership

codingsans.com

61–70 of 134 posts

Re: Soft Skills in Engineering Leadership

#61
post #58
post #44

Earlier quoted context omitted.

Companies like to claim this, but it's not the reality due to an imbalance in power between managers and IC engineers. A manager controls a reports salary, career progression, has more face time with VPs and so on. Software engineering is unique in that ICs can still scale to a similar level of impact as executives, but it is a mistake to think that a Staff engineer and Manager are equal in the eyes of the organizati…

> Software engineering is unique There is nothing special about software engineering as a technical track this way. There is no one way to set up an organization. To a large degree they are how they actually work (i.e. not what's on paper). This balance has been an issue in managing technical teams for about as long as that has been a thing, which is a lot longer than software has been a thing. There is a fundamental…

There is something special about software engineering because it is fundamentally about automation. As a result, an individual software engineer can create the sort of impact that traditionally would require a team.

I'm trying to make sense of the rest of your post, but it uses a lot of pronouns that don't appear to reference anything.

Re: Soft Skills in Engineering Leadership

#62
post #10

Earlier quoted context omitted.

I dont need managers to be coding. I do need them to have technical background and willingness to understand what tech is relevant to them - I had only bad experiences with non-technical managers. But I really dont understand why they should be coding. Even active developers are not able to fix whatever in any module, you fix only in areas you understand. When shit is on fire, I dont want managers or other random dev…

They should be coding because they're "engineering" managers. What's the point of having engineering in your title if you're not actually practicing the craft? They should be coding because they'll be able to relate to their supports in a deeper and more fulfilling way. They'll be able to mentor and provide guidance on technology best practices and patterns. They should be coding because they'll be able to more accur…

"Engineering" is more than coding and engineering managers can provide insights and value by demolishing higher-level roadblocks for their IC colleagues.

Re: Soft Skills in Engineering Leadership

#63

I've had some god awful managers in my engineering career and my managerial philosophy is twofold: have empathy and keep coding. Most, if not all, of my managers over the past 10 years have been people managers cloaked as engineering managers who have all stopped programming a decade ago. So much respect is lost for managers who have turned their back on the very craft that brought them into management. Before the pe…

I would just leave it at empathy personally. I've had technically minded managers, but my best manager actually empathized with the issues I was having and advocated for me when I needed it. She basically helped me handle non-technical issues to clear the way for me to do my technical work. When I needed technical help, she would assist in getting me the help I could if she shouldn't provide it. If I ever end up in a management position, I hope I can treat people in a similar way.

Re: Soft Skills in Engineering Leadership

#64
post #61
post #58

Earlier quoted context omitted.

> Software engineering is unique There is nothing special about software engineering as a technical track this way. There is no one way to set up an organization. To a large degree they are how they actually work (i.e. not what's on paper). This balance has been an issue in managing technical teams for about as long as that has been a thing, which is a lot longer than software has been a thing. There is a fundamental…

There is something special about software engineering because it is fundamentally about automation. As a result, an individual software engineer can create the sort of impact that traditionally would require a team. I'm trying to make sense of the rest of your post, but it uses a lot of pronouns that don't appear to reference anything.

> fundamentally about automation.

I agree software has more leverage, sometimes but we are talking here about how decision making power is distributed in a company.

Regardless about how much impact the IC technical output can have that is about how. The skills & information needed to make good decisions about what and when are different.

Unfortunately, being highly effective at both requires spending time and focus in ways that are somewhat mutually exclusive, which makes this quite hard.

Re: Soft Skills in Engineering Leadership

#65

Earlier quoted context omitted.

Well this was a very pleasant post to read as an autistic person. I can appearantly just have a lack of self awareness completely out of my control and this is embarassing, and demands harsh unpleasant words, even though this approach is likely to fail and inflict emotional trauma on me. "Empathy" after a social faux pas to me is kind of like a blameless post mortem. Blunt yet unjudgemental with a call to action and…

Usually a person with good empathy can pick up on social spectral disorders after some time and factor for this in their communications capabilities. This is often not a hard barrier. The problematic people are those that cannot self reflect AND are incapable of realizing the nature of their dilemma. The problem is present when a situation demands harsh words and the troubled person is utterly incapable of receiving…

> Usually a person with good empathy can pick up on social spectral disorders after some time and factor for this in their communications capabilities. This is often not a hard barrier.

There is no such thing as a perfect person who can do these things perfectly. There is such a thing as an imperfect person who BELIEVES they can.

It takes two to tango, and it takes a minimum of two to communicate.

Just this morning I had a quick discussion with a woman who asked me a question. When I responded with an explanation she realized I misunderstood (her question was meant to clarify an earlier statement of mine) and clarified, at which point I realized I read it more negatively than she intended. I acknowledged it and we both moved on.

Neither of us is super awesome or sucks, we're just two people trying to get through the day. We get along relatively well and this interaction neither diminishes nor exemplifies either of us. It's simply the human condition.

Acting as if you, by yourself, can be the sole arbiter of good, successful communication, is exactly why people often hate "people managers".

> If a person commits to an action that is potentially harmful they must be halted and corrected even at cost of some minor embarrassment. If that person then attempts that harmful action again they should be severely counseled. The harshness of the words should reflect the severity of the failure. Empathy doesn’t mean agreement or kindness which are akin to sympathy.

I don't agree with this either.

The big secret people don't want to acknowledge in terms of "people skills" is that if you can't get along with people who are significantly different than you, you don't actually have great people skills. It's easy to get along with people like yourself.

Time and time again I've seen a "people person" complain about someone else not having people skills and being difficult to work with.

What managers in particular need to understand is that they work with people all day, which is malleable. You can walk into a room and get what you want through sheer charisma and willpower. But Engineers work with reality. No amount of charisma and willpower will fix that bug, or keep that bridge from collapsing.

The result of this is a fundamental difference in values and worldview. The good managers recognize this and don't mentally accuse an engineer of being on the spectrum (and treating them differently as a result) and/or being difficult to work with because they don't appreciate their charisma over reality.

The real "secret" is to simply accept people for who they are. If that Engineer doesn't appreciate your charisma as much as you think they should, accept that they're trying to do a good job in their world and don't hold them in a negative light as a result. And don't try to manipulate them either, acceptance is not manipulation.

As for your specific example, calling people out in front of others is exactly what you DO NOT do. The better approach is to let it be unless it's bad enough that it needs to be dealt with. I say this because it allows the other person to approach the offender themselves. If you're REALLY worried about it, talk to the person it happened to and see how they feel. encourage them to approach the offender. If they're not the personality type to do that (dislikes confrontation) THEN perhaps you can facilitate that conversation.

In my 24 years in this industry I've only ever had a single person who did not apologize profusely when approached by me about something they said or how they were acting towards me. The typical response is roughly "I'm sorry, here's what I meant or what I was trying to do".

People don't set out to hurt others feelings. Oftentimes it's an accident because they're valuing something else, or they're in the heat of the moment. Communicate with them and allow them to communicate and you can often times create a better environment for everyone.

But calling them out in front of everyone? Not a good idea.

Re: Soft Skills in Engineering Leadership

#66

I've had some god awful managers in my engineering career and my managerial philosophy is twofold: have empathy and keep coding. Most, if not all, of my managers over the past 10 years have been people managers cloaked as engineering managers who have all stopped programming a decade ago. So much respect is lost for managers who have turned their back on the very craft that brought them into management. Before the pe…

Nope.

I don't need my manager to be a coder; I can do the coding. I need my manager to fight for me in our organization and to shield me and my team from various organizational BS. I don't believe that any of that has anything to do with coding ability.

Re: Soft Skills in Engineering Leadership

#67

Earlier quoted context omitted.

I don't understand why managers cannot fulfill both roles though? The job of management isn't hard (I'm doing it). Outside of the project management responsibilities, there is a lot of time doing nothing. If I wasn't coding, as a manager, 80% of the time I would sit around doing nothing. I strongly believe that managers should be able to fulfill both roles but maybe it's just because I've been burned by so many manag…

Question for HN: If you were talking with someone at a conference and heard him say > The job of management isn't hard (I'm doing it) What signals would you look for to tell the difference between these two possibilities? A. This person has so much tacit knowledge of good management that they don't realise how much skill they are applying day-to-day. B. This person has zero awareness of how their team is burning out…

Would you consider the possibility that you might have done it wrong all the time and all your previous managers taught you the wrong way?

Re: Soft Skills in Engineering Leadership

#68

Earlier quoted context omitted.

I don't understand why managers cannot fulfill both roles though? The job of management isn't hard (I'm doing it). Outside of the project management responsibilities, there is a lot of time doing nothing. If I wasn't coding, as a manager, 80% of the time I would sit around doing nothing. I strongly believe that managers should be able to fulfill both roles but maybe it's just because I've been burned by so many manag…

I'm going to pile on here with the others. If you're legitimately a people manager (not a low grade 'team lead'), there is no way, no how, you could have 80% free time. I've been doing this for some 23 years and had a stint as a proper manager for a year, where I spent about 20% of my time coding, and I was more starved for time than just about any other phase in my career. I'm currently a principal eng/ arch at a mi…

> general meetings, presentation prep, working on process improvements, Scrum/product owners for backlog grooming, interfacing with other managers, etc

You as a manager don't need to do all that. If you can't delegate most of that to reports then you have a problem.

Re: Soft Skills in Engineering Leadership

#69
post #44

Earlier quoted context omitted.

A manager is only a role model if the promotion structure is Engineer->Manager. At most modern tech companies that is not the main promotion structure. It's Engineer->Senior Engineer->Staff Engineer->Etc. Engineering management is a different path you can choose just like you can become a product manager but it is not the expected path.

Companies like to claim this, but it's not the reality due to an imbalance in power between managers and IC engineers. A manager controls a reports salary, career progression, has more face time with VPs and so on. Software engineering is unique in that ICs can still scale to a similar level of impact as executives, but it is a mistake to think that a Staff engineer and Manager are equal in the eyes of the organizati…

A title bump without the reporting structure changes to go with it is just a fancy way to dress up a raise, sure, but that's not the only option.

In companies doing this well, the high-level engineer doesn't report to the immediate team lead, but reports to the same director that lead does. Or VP vs director for even-higher-level engineers vs higher-level managers.

That structure, more than the title, is what shows you if you're really on an equivalent track.

Re: Soft Skills in Engineering Leadership

#70

Please don’t call them soft skills. If they weren’t hard, there’d be better leadership out there.

Soft skills means they are hard to measure. That is the original definition. Hard skills are easy to test, you either solved the problem or you didn't. With soft skills you don't really know, you need to measure it subjectively.
Post reply on HN