Another week, and I’m still stacking chips. Last week’s chips looked like this:

Intention

At the start of the week, I kept the same two goals from last week:

1. Rebuild hasworn so it is easily updated — ✅
2. Get back to gaming videos — ❌

Update

As you can see if you look at the Github activity logs throughout the week (Monday, Tuesday, Wednesday, Thursday, Saturday, Sunday) there was a lot of bitty activity on hasworn.

I like to publish neat, atomic, reasonably documented commits to git repositories, but the activity when I'm developing is much more like you see in the links above. Tiny commits, no explanations, frequent use of "fixup" (and not even proper fixups, just a commit with "fixup" as the title) and so on. Generally that would be what my code would look like locally, and then it would get rebased, tidied, and documented before pushing.

However, rather than trying to finagle my local changes to a remote server, I just relied on Github deploying my changes as I experimented. Then on the following Monday morning I rebased and rewrote the commits and force pushed that to be the new history of the repository. Not great behaviour in a collaborative environment, but then I'm the only one working on this codebase.

By the end of the week I had improved hasworn so it was serving the site on HTTPS, and building the user site with a full list of all tshirts worn by year, and showing a summary of the most worn tshirts on the homepage.

I also took a moment to release a new version of flourish so I could ensure I wasn't spending too much money on CloudFront.