4 ms·

> A bad software engineer means you need several other software engineers to clean up their mistakes. This also sounds like a problem with incompetent manageme

> A bad software engineer means you need several other software engineers to clean up their mistakes. This also sounds like a problem with incompetent management. If an engineer can spend so much time building bad code that it takes multiple engineers to clean it up, it means that there was a long history of ineffective code reviews and inadequate training (e.g., nobody bothered to give the engineer an overview of the architecture of the system they were hired to work on). And if the engineer is truly incompetent, it's also management's failure that the employee wasn't let go before they could create that amount of damage. Not to mention that management's interview process wasn't good enough to detect glaring incompetence. If management takes their jobs seriously, the risks of a bad hiring decision can be minimized to the point where it's not that risky to hire someone without a CS degree or inside connections.

Hamuko 7y ago
>And if the engineer is truly incompetent, it's also management's failure that the employee wasn't let go before they could create that amount of damage. In some places it's not that easy to get rid of people. I know there's someone at my current workplace who I secretly wish was let go, but I know that the only realistic option I have is find a new job myself.
hamandcheese 7y ago
Yes, in a well run organization it should be difficult for any one person to cause too much damage. Thats one of the benefits of bureaucracy! But at many startups, especially in the early stages, developers have a lot of autonomy (and rightly so). In a small environment like that, you need folks you can trust, and a mis-hire could be devastating.
deleted 7y ago
[deleted]
deleted 7y ago
[deleted]