Files are hard

Dan Luu · 12 Dec 2015

Dan Luu did not write this page.

Every claim below was made in this piece, quoted word for word and numbered in the order the piece makes them, so you can read it there rather than take our word for it. The sentence above each quote is our reading of the claim, not their wording. Each quote was checked against a stored copy of the page at build time; where the two differ, the quote is the fact.

Our reading
Writing to files safely is too hard to do with raw syscalls; application code should go through a library or a database.

Their wordsas an application developer, writing to files safely is hard enough that it should be done via some kind of library and/or database, not by directly making syscalls
Our reading
Conventional testing is not sufficient: crude purpose-built checking tools of a few thousand lines find bugs that testing does not.

Their wordsThese studies also hammer home the point that conventional testing isn't sufficient.
Our reading
Almost every software project has cheap testing wins left on the table: basic random testing, static analysis and fault injection pay for themselves the first time they are run.

Their wordsAlmost every software project I've seen has a lot of low hanging testing fruit.

Keep reading

The other pieces are the ones whose claims are worded most like this one's. That measures language, not agreement: they may argue the opposite.