use project zettelkasten to program
Table of Contents
The general workflow is this:
you write down the zettel for the program, this will be the top-level index for the project
title: portrait-gallary this program will create a gallary of portraits in HTML.
you write down feature stub zettels of the program in zettels and link them to the index.
title: infinite scrolling GUI tweak that when scrolling over the head of the GUI array, the tail of the GUI array would appear
implement the feature in zettels as snippets. if further decomposition of task or helper function is noticed, make zettels about them and link to them. Note that it is better to keep arbitary names in the zettel that use the helper function, rather the name of helper function, so:
title: click and drag + getX() <- ~[[getting mouse position in html container in js]]~
- why and to what it is better:
- you need to read the title - it has to make sense very quickly to you, you search notes on it
- closer to permanent - they can be put into main right away
- atomic - hides arbitary detail of “click and drag”. A coupling would be made if the name of the zettel with the mouse position snippet is called “getX” because “getX” is used in “click and drag”.
- why and to what it is better:
- research when further information is needed for the implementation, such as syntax, framework’s functions/objects, common practice, algorithms, etc.