The Construction Site

0000/00/00
todo, wip, draft, dev, alpha, beta, rc, idea
A bunch of texts may or may not be finished later

• [TODO] Just TODO
• [IDEA] 20201210-a-completely-incomplete-guide-to-computer-basics-part3-hardware-memory-&-disk.md
• [IDEA] 20200901-diy-dry-layered-docker-image.md
• • the docker usage
• • why layered works
• • size reduce hack
• • the core image and better cache sharing

[TODO] Just TODO

New doc idea:

• append-based data design
  • good in a file based store
  • less direct in the database (SQL mostly)
• concat-friendly data structures
  • JSON is good for never allowing unescaped /n and /r to exist as delimiter
  • gzip is good with a predefined magic header as delimiter
• the clearest and most basic design is often the best and minimal design to the problem
  • sometimes it's reasonable to further reduce the complexity by adding more artificial constraints, but think twice always, and don't invite those dropped burden back later, or you're just hopping to another truck full of garbage
  • it's important for the design to be real to the problem, rather than just be small, hiding too much often prepares later explosion cause by design mis-match, or being to limited
• The level-3 inception: docker in wsl2 in win10, and it's actually pretty good

Rant, sort of:

• browser:
  • max 6 ongoing tcp to the same site will block new connection, but using HTTP2 is hard.
• win10:
  • AppData/ is not the place for GameSave/UserData. If your game/program isn't cloud-only, save the file in your folder, or prompt for a folder.
  • Auto Driver Install Is the new Trojan, and can bring in GUI bloatware (ThinkPad in 2019), soon we may have new driver with Chrome or VirtualBox bundled inside.

[IDEA] 20201210-a-completely-incomplete-guide-to-computer-basics-part3-hardware-memory-&-disk.md

[meta:edit-log]: # "2020/12/10"
[meta:title]: # "A completely incomplete guide to computer basics - PART3 Hardware: memory & disk"
[meta:keywords]: # "code, guide, computer"
[meta:description]: # "Understanding this should be rather simple, after the harder previous part."

Register: fast, but why?

RAM: no memory without power

Disk: spinning

SSD: what actually do this mean?

[IDEA] 20200901-diy-dry-layered-docker-image.md

[meta:edit-log]: # "2020/09/01"
[meta:title]: # "DIY DRY Layered Docker Image"
[meta:keywords]: # "docker, image, layer, optimize"
[meta:description]: # ""

the docker usage

• good for dependency locking & trimming
• good for archiving reproducible procedure
• good for system file change diff (git for system)

why layered works

size reduce hack

the core image and better cache sharing