In my three years experience so far I can honestly say that 100% of the developers I've worked with are narrow sighted with regards to how they develop.

As in, they lack the capacity to anticipate multiple scenarios.

They code with one unique scenario in mind and their work ends up not passing tests or generates bugs in production.

Not to say I'm the best at foreseeing every possible scenario, but I at least TRY to anticipate and test my code as much as possible to identify problems and edge cases.

I usually take much more time to complete tasks than my colleagues, but my work usually passes tests and comes back bug free. Whereas my colleagues get applauded for completing tasks quickly but end up spending lots of time fixing up after themselves when tests fail or bugs appear.
Probably more time wasted than if they had done the job correctly from the start. Yet they're considered to be effecient devs because they work "fast".


  • 2
    Agreed. I kinda suffer from doing the short easy path sometimes when I have trouble sleeping (which is a lot lately) but whenever Im fully charged I try to test everything and even go an extra mile for the customer.

    Let me clarify that Im not really client-first oriented, but rather I try to imagine myself using the product and the usecases I can imagine using it for and take care of them in a UX pleasing way. So fuck the client and their deadlines, but I do like to make "good" things in be extension I get better tests and better experience for the end user whoever it is

    This also means that sometimes the extra effort costs more time and effort. But that's also why I push for slightly longer estimates on plannings. Not only to give myself space for inforseen issues, but also some polish and still finish on time
  • 4
    Nothing makes me wanna puke more than poor software design, can't tell what's what, stack overflow driven hacks getting passed for solutions, suboptimal performance, mediocre logic , unmaintainable code, ughh
  • 4
    Yeah many devs actually skip the design phase of writing code and just scramble shit until it "works". Who the fuck knows if it actually does what is needed though.

    I mean you don't need design for a small add-on or a small bugfix but for more complex tasks, you need research and design to understand the how, what and why.
  • 1
    @PepeTheFrog most devs just smash whatever snippets they googled into the project until it works, good luck with troubleshooting, now the code is just voodoo
  • 0
    @EpicofGilgamesh can't wait for this idiots to get wiped out by ai, it's can already copy and paste better than they can
  • 4
    "People get applauded for being fast" well there's your fucking problem.
  • 1
    Before long "my code has fewer bugs but people are being promoted over me"
  • 4
    I worked at a company that had zero unit tests before I introduced them. I usually write unit tests by going through the code from top to bottom and making a test case for each possible stop in the code. My code generally had very minor issues. Other seniors were constantly putting out fires
Add Comment