Of course we mostly solve problems by writing code
That's actually the most dangerous bias. More code is more maintenance, more bugs, more ways to pick the wrong approach. Solutions that reuse other people's code and especially to remove code are harder to take into consideration, because it is counter intuitive - like you're not doing your job.
Some common examples:
Catch-all exceptions instead of scream when broken
Not using that package, cause it has only 10 starts on github and we could do better
Not using a package, cause it does not do one or two things precisely as we want
Not removing code for edge cases that seemed likely to happen in a lifetime, but hasn't in the last year or so
Not removing code for platforms that no longer exist
Not removing code tailored to a customer that is no longer a customer and no one else needs it
The House of Cards syndrome: fear that removing seemlingly dead code breaks something elsewhere
Trouble maker and Problem solver ⚙️🔧
Loves simplicity, hates bullshit 💩.
Productivity obsessed, avid learner 🖥🚀
Sport and outdoor freak 🧗⛰
Metalhead 🎸🤘 Father of 2 👨👩👦👦
Opinions are my own
absolutely agree and like the points you listed!
it really sums up the idea of Negative Coding - ending your day pushing your changes to the repo, with less lines of code than before. if you found a better solution with less code, if you had opportuinty to simplify and remove clutter, you probably did a good job. even if it seems you didnt do much! :-)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That's actually the most dangerous bias. More code is more maintenance, more bugs, more ways to pick the wrong approach. Solutions that reuse other people's code and especially to remove code are harder to take into consideration, because it is counter intuitive - like you're not doing your job.
Some common examples:
absolutely agree and like the points you listed!
it really sums up the idea of Negative Coding - ending your day pushing your changes to the repo, with less lines of code than before. if you found a better solution with less code, if you had opportuinty to simplify and remove clutter, you probably did a good job. even if it seems you didnt do much! :-)