About code sketching

To fill in after writing up a more thorough blogpost

Why a Storybook?

(Bullet thoughts, will refine).

• Offline- enable "deep work" focus on code even if internet is down (Train, etc)
• Hybrid of an "inspiration board" with a git repository: sometimes you just need to browse what you've tried before
• Force engagement with new libraries as I encounter them, will retain better than just reading a tab
• Make it easier to try new technologies without needing having a full project justify some experimentation
• Keep the walls leaky (Blue making of video - walls not soundproof) to take key useful ideas from different visual frameworks, and combine them
• Gives me an excuse to dogfood StorybookJS
• Test hypothesis that having lots of knobs on most things is a good idea
• Reduce inertia of new project setup (needing to rerun CRA every time)

Administrative

• Click the ellipses to the left for the keyboard shortcuts + a searchable index of the code samples.
• Code snippets are not polished and liable to change at any time. I'll "graduate" them to another repository if they become shareable.
• When possible, I add controls for each sketch to the "knobs" panel.
• Resources are indexed by date, but organized by technology.

Queue

• See Readme for ideas, as well as package.json for aspirations
• Use d3-force to draw circles in processing (maybe others)?
• two.js
• Mapping
  • Kepler, deck, luma, etc
• Wallpaper Groups (Wikipedia)
• Music (tone.js)