Quotes About Documentation

The execution of any successful network project plan involves bringing all the pieces together, applying solid organizational principle to your network, and documenting what you add to your network.

The concept of preserving history, collating full archives, making them as usable as possible so the public have access to them, I really feel that it allows the public an ability to engage with their own history.

Our kids will never have to remember things, because it's all in pictures. Want to remember your fourth birthday? There'll be video of it on your phone.

The selfie makes us accustomed to putting ourselves and those around us 'on pause' in order to document our lives. It is an extension of how we have learned to put our conversations 'on pause' when we send or receive a text, an image, an email, a call.

If we do not, as historians, write the history of great events as well as the small stories that make up the past, others will, and they will not necessarily do it well.

If you are a plane-spotter, and you are interested in the history of a particular aircraft, you know there are many documents publicly available: registration papers and airworthiness certificates from the FAA. You can also get flight data from the FAA.

If you don't write it down, it never happened. - Roger Tory Peterson

Documenting the reasons behind requirements will give your team invaluable information when making daily implementation decisions.

Despite thorough testing, good documentation, and solid automation, things go wrong. Deliveries are late. Unforeseen technical problems come up.

We write code, which communicates our intentions to a machine and documents our thinking for future generations of developers.

Commenting source code gives you the perfect opportunity to document those elusive bits of a project that can't be documented anywhere else: engineering trade-offs, why decisions were made, what other alternatives were discarded, and so on.

There are certain tips and tricks that apply at all levels of software development, ideas that are almost axiomatic, and processes that are virtually universal. However, these approaches are rarely documented as such; you'll mostly find them written down as odd sentences in discussions of design, project management, or coding.

As programmers, we collect, organize, maintain, and harness knowledge. We document knowledge in specifications, we make it come alive in running code, and we use it to provide the checks needed during testing.

Did I say that? One says so many things, and the problem is they all get written down.

Life's been nothing but paperwork.

You have all these people in the city and everything has become centralized. If you live outside the city and you need a birth certificate or some official paper from the government, you have to travel to the city.

Behind every text footnote is a file folder with all the hardcopy documentation needed to document every sentence in this book at a moment's notice. Moreover, I assembled a team of hair-splitting, nitpicking, adversarial researchers and archivists to review each and every sentence, collectively ensuring that each fact and fragment of a fact was backed up with the necessary black and white documents.

Excessive record-keeping is a symptom of insecurity and defensive thinking. It indicates that you are less concerned attaining objectives than you are with documentation, and that your thinking is oriented to the past, not the present.

The actual judge reads the case, and accesses the documentation; thus, it focuses not on the links and contacts of a lawyer; otherwise, the judge fails to execute vitreous justice.

A lot of people think the best work I've done was nonfiction - the 'Brothers and Keepers' book. But I think of myself as a fiction writer. And I think, if my work is put in perspective, all the books would be a continual questioning of what's true and what's not true, what's documented and what's not documented.

I'm well-traveled. I've had to get a few passports because I ran out of pages.

I was in a band in the '90s called Bikini Kill, and we were so freaked out about documentation then, and there was the whole thing, not just about the male gaze, but that people were going to misrepresent you... a kind fear of the mainstream that a lot of us had.

The idea is every time I go to a show, that night or the next morning I write it down in the gig log. Sometimes they're very scant, sometimes they're very long.

Because the Vikings never documented anything - they couldn't read or write - the history is always gonna be a little up in the air.