4 ms·
the gatekeeping in software is sad. why is it that so many in our field feel that gatekeeping and always being correct, to the point of aggressive confrontation
by mylons 6y ago
the gatekeeping in software is sad. why is it that so many in our field feel that gatekeeping and always being correct, to the point of aggressive confrontation, is the way to do this? are we all that insecure?
- adsjhdashkj 6y agoI think to some degree there's usefulness in gatekeeping titles - as titles could be a great way to know areas or level of expertise. Key word "could" be. Unfortunately the nature of language combined with personally assigned titles means that there's no point in even trying because, i think, it's impossible. Call yourself whatever you want. I'm still going to need to vet it for myself if i need to hire you.
- mylons 6y agotitles are often just a way to make an employee feel self important without giving them a raise. see pmarca and zuck discussing this.
- arwhatever 6y agoDavid Parnas explained in an interview: Q: What is the most often-overlooked risk in software engineering? A: Incompetent programmers. There are estimates that the number of programmers needed in the U.S. exceeds 200,000. This is entirely misleading. It is not a quantity problem; we have a quality problem. One bad programmer can easily create two new jobs a year. Hiring more bad programmers will just increase our perceived need for them. If we had more good programmers, and could easily identify them, we would need fewer, not more. ... most software developers will have direct exposure to/experience with one or more such incompetent programmers.