kamo
/
thesis
1
2
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
main
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '08f05be8ec'
${ noResults }
thesis/carpet/provisional_text_dump.md

920 B
Raw Blame History

Provisional txt dump

Software without documentation

Software without documentation is invisible.

Therefore it is important to document it. Software without documentation tends to slip away, to disappear. Therefore it is important to have some notes on how does it work, how does it tackle the problem to solve.

These guidelines are helpful when sharing programs with others, as well with future selves. They provide an entry into the messy relationship between developers and machine.

bonus caption for eventual images

Being programming slightly different from cycling, people tend to forget what their code does, and how did it get there. (Maybe because it doesn't involve muscle memory?)

Software documentation is a defensive mechanism operated from our past selves to protect the present and future ones.

Cuneiform writing and comments. (even though this is cuneiform writing and syntax highlighting)