News for hackers. Stuff that matters.
Re:Outraged about the Google diversity memo? by mberning on Thursday August 10, 2017 @12:32AM (#14976374)
I like the discussion. I think the point about software being significantly "people centric" is a bit off base and betrays the authors lack of experience in the field. Working with people is certainly part of the job and in some roles maybe a large portion of the work. Being a good communicator is an important part of being a good developer, but it doesn't make you a good developer. Being a talented and experienced programmer is the foundation on which the rest is built.
Re:Outraged about the Google diversity memo? by michaelchisari on Thursday August 10, 2017 @02:19AM (#14976958)
Being a talented and experienced programmer may be the foundation, but the ability to communicate complex ideas in accessible ways, to read the room and respond to non-verbal cues, to put aside ego, to collaborate and coordinate, to sense frustration or unhappiness in your team, without those, you don't get past the first few stories of a skyscraper.

The longer I'm in the field, the more I work with different teams, the more I realize that writing code is a much easier skill for people who don't know to learn than reading people is for those who can't seem to.

Re:Outraged about the Google diversity memo? by generic_user on Thursday August 10, 2017 @04:05AM (#14977447)
Most of the skills that you listed only start to really matter if you try to move into a management position.

No company or project wants rank and file programmers (which is the vast majority of any project) who think there also managers and act as such. Even if you have those skill your job is to focus on your tasks and solve your very specific problems, not the big picture and what everyone else is doing.

Re:Outraged about the Google diversity memo? by michaelchisari on Thursday August 10, 2017 @04:09AM (#14977475)
I emphatically disagree. All of those skills are necessary to be a strong team member, and thinking that only management requires them is to move into territory where programming as a trade is in need of micro-management and social babysitting by a managerial class.

I've been in plenty of teams that were extremely flat exactly because the programmers in those teams were all highly skilled in those areas.

Re:Outraged about the Google diversity memo? by pink_duck on Thursday August 10, 2017 @05:07AM (#14977841)
I have just joined the workforce after uni, and it has never been more clear to me that what you're saying about communication and "people skills" is correct. Almost all of the issues that the company that I work for have are based on lack of communication skills, lack of empathy, too much ego etc.

It reminds me of what a coed wrote to me once about the difference between a good developer, and two ok ones.

"2 < 1+1"

Basically, even if you're higher ranked intellectually speaking and do more work than the average worker alone, two people that can perform adequately and that work together will outperform you.

Cooperation is key, and people need to be trained to do better handle that part of the job. Not just produce code.

</end-rant>

Re:Outraged about the Google diversity memo? by nd7287z on Thursday August 10, 2017 @06:15AM (#14978196)
This claim is entirely unsubstantiated. In fact it is pretty much the opposite of the theses in Fred Brooks' "Mythical man month".

I'm not saying Brooks is 100% correct, but his observations are close to what I am seeing in the field.

Re:Outraged about the Google diversity memo? by pink_duck on Monday August 14, 2017 @05:21AM (#15007440)
I wouldn't consider my claim any more unsubstantiated than other observations made by a developer, for instance you. I haven't read the book that you refer to, but it seems like Brooks's law (which according to Wikipedia is the central theme of the book) is talking about already late projects. For those, or any already ongoing project, I agree that adding more people will require ramp up time, but I am not talking about late projects alone. I think that for development in general, using something like pair programming instead of the lone, rock star developer, will lead to better code in the end (https://collaboration.csc.ncsu.edu/laurie/Papers/XPSardinia....).

Further, his second point about communication issues is to some extent proving my, and michaelchisari's point. Communication is a skill that is essential, but not stressed enough. If people were better at "communicate complex ideas in accessible ways", as michaelchisari originally put it, then I think it's likely that Brooks' wouldn't have the second argument to support his law (https://en.wikipedia.org/wiki/Brooks%27s_law).

Essentially, I think it comes down to where we work, what we assume about a project, and how the issues in these projects are best tackled.

At my work, better communication would have lead to less work in the long run. This because team leads couldn't clearly state their requirements, the different parties thought they agreed, and work was made that wasn't originally intended by team leads. Moreover, no one that holds a senior position is willing to acknowledge that these communication issues often are two way streets and that they are equally responsible for the miscommunications that happen. They also talk badly about others and have a serious case of hubris, which means that other peoples opinions are looked down upon or sometimes not even listened to. Basically lacking a lot of the skills that michaelchisari originally listed.

I hope that this clears out any "unsubstantiated" parts of my original rant for you.

Re:Outraged about the Google diversity memo? by michaelchisari on Thursday August 10, 2017 @05:18AM (#14977912)
Your observations are correct, and the more you can nurture those skills in yourself and others right alongside the ability to optimize algorithms and learn new frameworks, the faster you will leave the programmers who don't think these "soft" skills are useful very quickly behind.
Re:Outraged about the Google diversity memo? by generic_user on Thursday August 10, 2017 @05:10AM (#14977867)
Its a question of degree. Yes you have to have 'some' people skills to be a programmer in a team but its a small amount of skill. In a group of people that probably has more in common with you than any other group you have to interact with in life.

But its much less people skills then a manager, in meetings most of the day resolving issues that are much higher level that involve different departments etc.

So your average programming job is well within the social skills of the vast majority of Men. When your evaluating a pool of potential hires its going to be 95% finding the best programmer and then the last 5% is making sure there not crazy or a drug addict etc.

Its never going to be the case that you start out with a pool of resumes from people with really nice personal bios and try and find out which ones can program a computer.

Re:Outraged about the Google diversity memo? by tyingq on Thursday August 10, 2017 @12:42AM (#14976436)
>Being a talented and experienced programmer is the foundation on which the rest is built.

I think that is sometimes true, sometimes not. Certainly there are mediocre developers thriving because they are good communicators. I see this often in niche spaces like "POS software for Pet Stores". They thrive because they can communicate well with the customers and create something that does what the customer wants. Even if the internals are a horrid spaghetti mess that's inefficient, took longer to write than it should have, is hard to maintain, etc.

Re:Outraged about the Google diversity memo? by ebola1717 on Thursday August 10, 2017 @12:37AM (#14976411)
That's a nice theory, but I fail to see any evidence of it. I see lots of people cap out at senior engineer, cause that's how far you can get without having strong technical skills. Staff engineers, tech leads, and managers all get there because they're good communicators, and tbh, in those roles, their engineering skills are secondary.
Re:Outraged about the Google diversity memo? by mehwoot on Thursday August 10, 2017 @02:59AM (#14977124)
I see lots of people cap out at senior engineer

What's wrong with that? The majority of software engineers are senior engineer or below, any skill you only need to make it past that level clearly can't be considered core to the job.

Re:Outraged about the Google diversity memo? by mberning on Thursday August 10, 2017 @12:48AM (#14976485)
If middling engineers end up in senior development positions I wonder where all the top performers go... certainly not 100% into management.
Re:Outraged about the Google diversity memo? by selimthegrim on Thursday August 10, 2017 @07:14AM (#14978500)
Surely you meant strong people skills?
Re:Outraged about the Google diversity memo? by yellowapple on Thursday August 10, 2017 @12:49AM (#14976490)
Being a talented and experienced developer means interacting with people, though. Knowing how to program is half the battle; knowing why is the other half, and that's hard to do if you don't understand the perspectives of your users/customers/coworkers/etc.
Re:Outraged about the Google diversity memo? by mberning on Thursday August 10, 2017 @01:04AM (#14976588)
Knowing how to program is most of the battle. Being a good communicator helps. If your predominant skill was dealing with people you would be working as a BA, PM, or other similar role. Most businesses aren't stupid enough to pay a developer salary to somebody not actually doing development.
Re:Outraged about the Google diversity memo? by ebola1717 on Thursday August 10, 2017 @02:12AM (#14976922)
Developing is communicating, especially at a large company like Google. Anytime you're building a new feature, you have to reach out to stakeholders, write docs, and build consensus. I've been working as an engineer for years, and I've progressively spent less time coding and more time consensus building. The staff engineers I know spend even more of their time doing that, not to mention mentoring other teams, reviewing technical designs, etc.
Re:Outraged about the Google diversity memo? by nippples on Thursday August 10, 2017 @02:05AM (#14976892)
The confusion comes in the lack of distinction between software programming and software design in these discussions. The former values mathematical thinking, the latter values understanding how much the user will fuck things up for everyone.