This post is to filter the ‘boring’ stuff away from pages regarding progress like new milestones. I don’t mean to explain milestones, but to make the public understand I treat them differently on this site, distilled for minimal noise, for maximum signal!
What to expect from every milestone post?
Milestones are actually externalized milestones. Internal milestones… well, I am pretty sure the public doesn’t want to see a weekly digest of my 8 whopping KANBAN boards entailing progress on tech-level design, software architecture, deep engine internals and creation pipelines for both the code and art. We’d be talking about EDA architectures, caching systems, code abstraction levels and I must hit my own pause button there – it’s crazy enough that I personally hold my individual retrospective and sprintplanning every monday, just to keep my mind’s context aligned for the upcoming week. This blog here has the same effect as I sanity-check more parts of the process. After all, when it’s externalized, it’s ‘out there’ and it’d better make sense.
Also, I’d be spending more times blogging whilst I could have completed yet another milestone after a while. I mean, I’d have to distill information from this:
Do you rather want to see more technical internals as it’s perhaps interesting after all? Well, that’s where this post is for – share any feedback about the level of detail here if needed. For now I think the current balance is just fine.
– Litanic
Discover more from STEENVAL STUDIOS
Subscribe to get the latest posts sent to your email.