--- title: "One Commit, One Small Site: What a Quiet Week Teaches You" description: "One commit this week: a data refresh on a small static site. What a slow week looks like from the inside of a one-person shop." url: https://theapparchitect.com/blog/2026-09-07-weekly-update/ language: en last_modified: 2026-10-15T13:12:46.000Z --- Notes — Sep 7, 2026 — 4 min read # One Commit, One Small Site: What a Quiet Week Teaches You One commit this week: a data refresh on a small static site. What a slow week looks like from the inside of a one-person shop. - hire app developer - build-in-public - astro - static-site - solo-developer One commit this week. Not the autopost kind, but an actual content update. The cached feed data on a small static site I maintain was stale, so I ran the refresh script and pushed. That was it. One green square on the graph for seven days. I am not going to dress that up as a productive sprint. It was a quiet week, and I think writing honestly about what that looks like is more useful than skipping the post. ## What Actually Moved: a static-site data refresh I built and maintain the site. It runs on Astro, in a private repo. It pulls external feed data at build time and caches it statically, which means the embed section can go stale if I do not refresh it periodically. That is not a flaw in the architecture. It is a deliberate trade-off. Static-first means fast, predictable, cheap to host. The downside is that “fresh” requires a manual trigger or a scheduled refresh pipeline. I do not have the scheduled pipeline in place yet for this site. I have been meaning to wire one up (a simple scheduled job that fetches the latest metadata and triggers a rebuild), but I have not done it. So right now, “refresh the data” means me noticing, running the script, and pushing. One commit, done in four minutes. Honest take: the manual step is fine for now. The source does not change every week. But the right long-term answer is a lightweight automation that checks for new content on a schedule and only rebuilds when something has actually changed. That is probably a few hours of work. I keep deprioritizing it because the manual approach has not caused a real problem yet. That is exactly how technical debt starts. ## What a Slow Week Actually Signals I want to be direct about something. A week with one commit is not a sign that the shop is idle. Client work, architecture thinking, conversations with potential clients: none of that shows up on a contribution graph. This week had real conversations in it. A call about a booking system for a small service business. Some thinking about how to restructure the services I offer for clients who are not quite ready to commit to a full build but want to move past spreadsheets. None of that is a GitHub commit. But it is the work that leads to a project, which leads to a commit history that looks a lot busier than this one. If you are a small business owner considering custom app development, the honest thing I can tell you is this: the quietest weeks in a solo shop are often the ones where the important conversations happen. A slow commit graph is not the same as a slow developer. It sometimes just means the work is happening off the keyboard. What I do think matters, and what I try to demonstrate here week by week, is that I show up and write the post even when the week was thin. That consistency is more useful information than a padded activity summary. You are reading the real version. ## What Is Next The refresh automation for that site is on my list for next week, assuming nothing larger comes in. I also want to take another look at the booking flow on theapparchitect.com. I have a nagging feeling the Cal.com embed is creating a small amount of friction on mobile that I have not properly addressed since the [August rebuild](https://theapparchitect.com/services/). Neither of these is a major project. But small, deliberate improvements add up. That is most of what maintaining real software actually looks like. If you are thinking about having a site or app built and want to talk through what that would involve, the fastest way to reach me is the booking link on the [contact page](https://theapparchitect.com/contact/). ## More on this topic - software architecture ### [Static-First Costs: The Refresh I Keep Doing by Hand](https://theapparchitect.com/blog/2026-09-28-weekly-update/) Two commits this week. A static site needed another manual data refresh, and I still haven't built the pipeline that would fix that. Read more - hire app developer ### [One Commit, One Autopost: What Showing Up Every Week Actually Means](https://theapparchitect.com/blog/2026-07-20-weekly-update/) One autopost commit this week. What an empty GitHub graph means for a solo developer, and why consistency is the signal clients actually read. Read more - hire app developer ### [The Punctuation Edit: Why I Rewrote the Tone Across Three Sites](https://theapparchitect.com/blog/2026-08-10-weekly-update/) Four commits this week and one editorial call that touched every site I own: why replacing em-dashes matters more than it sounds. Read more