"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
-
-
Replying to @CodeWisdom
Usually the problem really is, "this library doesn't do X the way we need to do X." We need X but faster, or higher precision, or X with Y.
1 reply 0 retweets 11 likes -
Replying to @Daveisanawesome @CodeWisdom
Or you just have no practical way of verifying that lib X actually, correctly does what it claims to. Verifying is costlier than writing.
1 reply 1 retweet 13 likes -
Wouldn't you still incur the verification cost on your own code? Or is it more about tricky instantiation or integration?
1 reply 0 retweets 1 like -
Often third-party library code does not even document its interface contracts, failure/corner cases, etc. You have to RE all that.
1 reply 0 retweets 0 likes -
Replying to @RichFelker @sebjcarroll and
Verifying your own code is hard but less so, & also less necessary since you at least know the specification it was written to.
1 reply 0 retweets 0 likes
You also know you have access to the development history (& usually the people) behind it if/when there is a problem.
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.