Automated dependency updates
Keep dependency updates automated so they stay small, safe, and manageable.
Archive
Short essays, implementation notes, and design decisions from my work on tools and websites.
Keep dependency updates automated so they stay small, safe, and manageable.
My personal default is to use GitHub Actions for CI/CD until a better alternative clearly earns the switch.
Write broadly first, then come back later and decide what deserves depth.
Build automations from loose, high-level blocks that are easy to chain and change.
Write about what is being built so people can find it through search.
Major goals need measurable key results, even when the measure is only a proxy.
Notes hold general ideas; projects hold concrete tools that may later point to a website or GitHub repository.
Keep the number of simultaneously open projects small enough to stay focused.
Why planning on paper or with sticky notes often works better than planning on a screen.
A personal bias toward building when the goal is learning, experimentation, and hands-on work.
Keep process small enough that it still helps the work move forward.
Why planning and implementation need separate mindsets.
How I keep small internal tools simple enough to maintain.
A reminder to move ideas from notebooks and to-do lists onto the website.
Why I want my implementation notes to be readable outside my own head.