Re:Ask HN: What are some bad developer habits?
by malux85 on Friday June 14, 2019 @01:06PM
(#20184591)
- Wrong level of abstraction (too high level, too low level) either in verbal communication or coding.
- Intellectual violence (agressivness to people in meetings because they know the details someone else might not know)
- Hoarding knowledge - Incorrectly assuming it makes them more valuable rather than seeing the big picture that there's an infinite amount of knowledge out there and we are better to spread it as far as possible.
- Refusal to learn new tools and using the same old stack over and over again, even if it's an inappropriate choice
- Always leaning new tools, and never finishing / shipping
- No README or build instructions. Not testing to make sure builds work off their personal machine
- Looking down on others that dont know X, even though they didn't know X 5 minutes ago.
- Getting defensive about the codebase rather than remembering we are all on the same team.
- Leaving the code in a worse state than they found it in.
- Championing a new technology choice because it's the new hotness, then refusing to take responsibility for it when it turns out to be unstable or problematic
- Never admitting fault or that they might be wrong
- Willful blindness to policy or ethical violations
- Sanctifying the code / sunk cost fallacy -- thinking that code is somehow sacred or deserves special treatment because it took them a while and effort to write : sometimes you have to just throw it away, rather than keep pushing resources into something that isn't working and refusing to give up because you've already put so much effort in.
- Intellectual violence (agressivness to people in meetings because they know the details someone else might not know)
- Hoarding knowledge - Incorrectly assuming it makes them more valuable rather than seeing the big picture that there's an infinite amount of knowledge out there and we are better to spread it as far as possible.
- Refusal to learn new tools and using the same old stack over and over again, even if it's an inappropriate choice
- Always leaning new tools, and never finishing / shipping
- Softare engineering anti-patterns https://en.wikipedia.org/wiki/Anti-pattern#Software_engineer...
- No README or build instructions. Not testing to make sure builds work off their personal machine
- Looking down on others that dont know X, even though they didn't know X 5 minutes ago.
- Getting defensive about the codebase rather than remembering we are all on the same team.
- Leaving the code in a worse state than they found it in.
- Championing a new technology choice because it's the new hotness, then refusing to take responsibility for it when it turns out to be unstable or problematic
- Never admitting fault or that they might be wrong
- Willful blindness to policy or ethical violations
- Sanctifying the code / sunk cost fallacy -- thinking that code is somehow sacred or deserves special treatment because it took them a while and effort to write : sometimes you have to just throw it away, rather than keep pushing resources into something that isn't working and refusing to give up because you've already put so much effort in.