"Telling a programmer there's already a library to do X is like telling a songwriter there's already a song about love." - Pete Cordell
-
-
Wouldn't you still incur the verification cost on your own code? Or is it more about tricky instantiation or integration?
-
Often third-party library code does not even document its interface contracts, failure/corner cases, etc. You have to RE all that.
-
Verifying your own code is hard but less so, & also less necessary since you at least know the specification it was written to.
-
You also know you have access to the development history (& usually the people) behind it if/when there is a problem.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.