3 ms·

> At best, he’s a middling performer; his code is a mess (initializing variables that are never used, using variable names no one else understands, etc.), he ta

> At best, he’s a middling performer; his code is a mess (initializing variables that are never used, using variable names no one else understands, etc.), he takes longer than he should, and he doesn’t even remember his own code months later. Not everyone is a top performer. If you're a large software company you're going to have lots of 'average' people. The "his code is a mess" is hard to qualify. Variables that are never used and no one understands? So this imaginary large software company doesn't use an IDE or linters of any kind? That seems quite unlikely. He takes longer than he should? Because he's average and you're holding him to an above average standard? Or you've overloaded him with work which is quite likely. >Dunning-Kruger Effect An unproven hypothesis that is often misapplied and is absolutely misapplied in this case. This 'large software company' is clearly the major failure in this article and not some random engineer.

Chris2048 6y ago
> you're going to have lots of 'average' people Yes, by definition there will always be an average. But "average" for employed s/w devs should differ to national average - you can still expect developers to maintain certain standards, and that higher-ups will perform better (than say, the average s/w grad).
- sleepysysadmin 6y ago
  >Yes, by definition there will always be an average. But "average" for employed s/w devs should differ to national average - you can still expect developers to maintain certain standards, and that higher-ups will perform better (than say, the average s/w grad). I dont disagree. The article to me reads differently. Like the author was digging for 'failures of a developer' but only proposed issues that are for sure failures of the company. I expect the entire article is horseshit. A scenario that was invented in this dude's mind. Out of interest I just checked out the authors other articles. Topics ive noticed is Emotional Intelligence, burnout, racial/sexual discrimination, and performance reviews. This guy has little to no clue about the tech side. He doesn't understand maintaining standards or how any of the software development process works.

Chris2048 6y ago

> you're going to have lots of 'average' people Yes, by definition there will always be an average. But "average" for employed s/w devs should differ to national average - you can still expect developers to maintain certain standards, and that higher-ups will perform better (than say, the average s/w grad).

sleepysysadmin 6y ago
>Yes, by definition there will always be an average. But "average" for employed s/w devs should differ to national average - you can still expect developers to maintain certain standards, and that higher-ups will perform better (than say, the average s/w grad). I dont disagree. The article to me reads differently. Like the author was digging for 'failures of a developer' but only proposed issues that are for sure failures of the company. I expect the entire article is horseshit. A scenario that was invented in this dude's mind. Out of interest I just checked out the authors other articles. Topics ive noticed is Emotional Intelligence, burnout, racial/sexual discrimination, and performance reviews. This guy has little to no clue about the tech side. He doesn't understand maintaining standards or how any of the software development process works.