4 ms·

So, I'm trading potentially error-prone if statements that are plainly visible in the code for a potentially buggy library whose code I'm not familiar with just

• ainar-g 8y ago
  Notice how OP had to add a check after verifying two pointers against nil. A junior developer could've easily skipped it, and, if tests only go through happy paths or are non-existent, deploy it somewhere where it would explode in runtime.
  • chooseaname 8y ago
    > A junior developer could've easily skipped it... But the senior developer should catch it in a review before ... > ...deploy it somewhere where it would explode in runtime.
    • Groxx 8y ago
      I have yet to work anywhere with sufficient senior developers to cover every single chunk of code. And review misses stuff all the time regardless.
    • UncleMeat 8y ago
      Computers are much better at consistently catching errors than developers
• fernandoalmeida 8y ago
  The whole library has 199 lines (with comments), and the code is very clear (at least, for me). You can give a try to read it.