One commit this week. Not the autopost kind — an actual content update. Monday morning the YouTube feed data on jasminelise-beauty.de 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: jasminelise-beauty.de
Jasmine Lise Beauty is a beauty salon site I built and maintain — Astro-based, private repo, live at jasminelise-beauty.de. The site pulls YouTube video 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 cron job that fetches the latest YouTube metadata and triggers a rebuild — but I have not done it. So right now, “refresh YouTube data” means me noticing, running the script, and pushing. One commit, Monday morning, done in four minutes.
Honest take: the manual step is fine for now. The salon does not post new videos 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 an afternoon 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 YouTube automation for jasminelise-beauty.de 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.
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 /contact.