“When speaking of disabilities, the blind and their needs are most often used as an example. It is deceivingly simplistic since accessibility is something most of the population can benefit from. We all benefit when we are tired, in bright sunshine with a mobile, are forced to use a gaming mouse with too-high sensitivity or receive the text version of video clips when we have forgotten our earphones and are in a quiet environment.” ― Marcus Österberg, Web Strategy for Everyone
“If debugging is the process of removing software bugs, then programming must be the process of putting them in.” -Edsger Dijkstra
“Walking on water and developing software from a specification are easy if both are frozen. ” - Edward V Berard
“ It's not at all important to get it right the first time. It's vitally important to get it right the last time.” - Andrew Hunt and David Thomas
A codebook describes the contents, structure, and layout of a data collection. A well-documented codebook “contains information intended to be complete and self-explanatory for each variable in a data file".
Codebooks begin with basic front matter, including the study title, name of the principal investigator(s), table of contents, and an introduction describing the purpose and format of the codebook. Some codebooks also include methodological details, such as how weights were computed, and data collection instruments, while others, especially with larger or more complex data collections, leave those details for a separate user guide and/or data collection instrument.
“Remember, the web isn't about control. If a visitor to your site is familiar with using a browser's native form doodad, you won't be doing them any favors if you override the browser functionality with your own widget, even if you think your widget looks better.” — Jeremy Keith