Like it or not, dealing with people effectively and respectfully is an important part of software development.
There are certainly vital roles for Developers who want to remain technically focused at the complete expense of human interaction, but (like it or not) it will limit the opportunities open to them.
I would suggest that acting as the public face of a gatekeeping process is the wrong role for anyone who doesn't like dealing with people and/or has trouble interacting with them politely or helpfully within the time available.
Perhaps the role would be better split between two people: a public-facing person and a purely technical gatekeeper. The gatekeeper then only has to deal with the public-facing person, who can provide potential contributors with help, assistance, and common human decency, as well as acting as a first level filter. That seems like a win-win for everyone.
Comments
Like it or not, dealing with people effectively and respectfully is an important part of software development.
There are certainly vital roles for Developers who want to remain technically focused at the complete expense of human interaction, but (like it or not) it will limit the opportunities open to them.
I would suggest that acting as the public face of a gatekeeping process is the wrong role for anyone who doesn't like dealing with people and/or has trouble interacting with them politely or helpfully within the time available.
Perhaps the role would be better split between two people: a public-facing person and a purely technical gatekeeper. The gatekeeper then only has to deal with the public-facing person, who can provide potential contributors with help, assistance, and common human decency, as well as acting as a first level filter. That seems like a win-win for everyone.
Edit: Just spotted that avivo already suggested this. https://news.ycombinator.com/item?id=8922331