Notes

• A globally-available filesystem is a security liability
• A globally-available filesystem prevents access tracing
• A good hyperlink has enough context to work around broken URLs
• A microservices architecture is object-orientation with big objects
• A “users” table is a smell
• Artificial slowdown as a way to guide deprecation
• Asynchronous working environments make it easier to divide up time
• Avoid naughty words in hex digest strings by changing the set of characters
• Budget for replacing past purchases
• Code in a good programming language does not reveal its author
• Factorio teaches you about tech debt
• For a good gaming session, set a goal
• Get people on board with breaking changes by radiating intent
• Good human-usable tokens are not random strings
• Logging and caching are (usually) acceptable side effects
• Naming principles
• Nanoc needs --json so that the CLI can be used programmatically
• Nanoc needs file paths to be known before compilation starts
• Nanoc sites take too long to load
• Nanoc’s terminology is inconsistent with the industry
• Nanoc’s use of Ruby is not an appealing choice these days
• Offices and creativity are at odds
• Organize electronic archive by year
• Phrase suggestions as open questions
• Ruby can be slow for short-running apps because it needs to load (require) dependencies
• Spreadsheets are fragile because they only deal with cells
• stderr is for diagnostic output, not errors
• Taking a break is better than excess context switching
• The filesystem is global mutable state
• There are many embedded plaintext metadata formats
• Use Docker tags to document the lifecycle of an image
• “Mirroring” is using hyperlinks for the mind