13 ways to be a lousy developer: - Don't volunteer to help others
13 ways to be a lousy developer:
- Don't volunteer to help others.
- Don’t try to get better or learn.
- Don't test code before opening a PR.
- Rubber stamp PRs, or don’t review them at all.
- Don't be proactive. Only act when told to do so.
1/5 👇
- Write hacky, buggy, hard to understand code.
- Often fail to finish work. Give up if it’s hard.
- Don't use personal judgement. Only do precisely what you're told.
- Be hard to contact during the day and frequently unavailable.
2/5
- Open PRs that take more time to fix than it would to just redo it.
- Frequently complain. But don’t suggest or implement improvements.
- Consistently take far longer than expected to finish tasks.
- Fail to take responsibility. Blame failures on the system or others.
3/5
Harsh truth: Some developers are lousy.
They do merely enough to keep their job. They’re content with doing mediocre work, slowly.
Their work looks like they don’t care...because they don't.
4/5
A lousy dev can be a net loss for the entire team's productivity.
Why? Working with someone who doesn't care demotivates whole the team. Their behavior and attitude is demoralizing.
The solution? Try to fix their behavior. But if that fails, fire them.
</thread>