A Screenshot Is Not a Case Study Until It Explains SomethingA project image answers one narrow question: what did this interface look like in this state? It does not tell me whether an API request succeeded, whether a keyboard user can complete a task, or whetSep 13, 2026·4 min read
Runbook Thinking for Full-Stack ProjectsWhen I think about software documentation, I often think about operational runbooks first. In field operations, a runbook is useful because it reduces guesswork. It gives the work a structure: what toJul 22, 2026·2 min read
README Documentation Habits I Use in Full-Stack ProjectsA README is one of the first places I look when I want to understand a project. That is true for other people's repositories, and it is also true when I review my own work. I want a project README to Jul 21, 2026·2 min read
Project Planning Before Code: A Practical Full-Stack HabitI try to treat planning as part of the build, not as something separate from development. Before I start writing code, I want to understand the workflow, the user path, the data, and the first useful Jul 20, 2026·2 min read
Checklists, Handoffs, and Reliable Software WorkflowsReliable software work is not only about writing code. It is also about leaving enough context for the next decision. That idea connects directly to what I have learned in field operations. In water-tJul 15, 2026·2 min read
Technical Communication Lessons from Full-Stack ProjectsWhy communication matters in technical work When I work on software projects, I keep coming back to the same lesson: a working feature is only part of the job. The next person also needs to understandJul 14, 2026·2 min read
Book Buddy Project Notes: React, Vite, API Workflows, and Account ActionsBook Buddy is one of the projects Frank Smith III uses to practice the front-end side of full-stack development: connecting a React client to API-backed user workflows and keeping the interface focuseJun 17, 2026·2 min read
