studio status report: 2026-07

Month 07 of 2026 was about releasing kintespace.com, really digging into details of Microsoft’s inflation of cloud rental costs and formally experimenting with Astro. Yes, kintespace.com was finally released on the 10th day of the month–but let’s see whet…

studio status report: 2026-06

I have not yet released kintespace.com—but shortly after I am done writing this report, it should be released to staging for testing. This was the most lengthy, self-imposed task of my entire adult life. …and, sorry capitalism (and sorry me), this “great …

studio status report: 2026-05

I have not yet released kintespace.com. I am still working on the Index (home 🏠📄): kintespace.com Index page What is left to do (generally—without rabbit holes 🐇🕳) are a few bits: - use a flowing flex layout of ‘visitor thumbs’ in the space visitors s…

studio status report: 2026-04

Month 04 of 2026 witnessed the continued lack of the re-release of kintespace.com—still almost out the ‘door.’ This month was dominated by two blockers: 1. an illness that lasted over a seven days 2. errands and meetings required in response to losing my …

studio status report: 2026-03

Month 03 of 2026 continued not getting the re-release of kintespace.com almost out the ‘door.’ This delay is well within the realm of inexcusable! Here were my alleged blockers: - At the beginning of this month, I wrote in my notes, ’The time is long over…

studio status report: 2026-02

Month 02 of 2026 was still about not getting the re-release of kintespace.com almost out the ‘door’—just like last month! But the main reason for this extravagant delay (apart from more #day-job tech drama) was my major discovery of the ‘magazine cover’ l…

studio status report: 2026-01

Month 01 of 2026 was about not getting the re-release of kintespace.com almost out the ‘door’—even though well over 90% is done! The month was mostly spent on #day-job drama, including: - a new understanding of DDD aggregates and how Entity Framework supp…