Block 3, second part: the more technical side of pipelines.
This week had more numbers in it than the previous one. LOD math, texel density, mesh instancing, texture compression. That shift felt right. The first half of this block was mostly conceptual and process-driven; this half had to justify the decisions with actual values. That's a different kind of writing and a harder one, but I think it's more useful.
What clicked
The texel density posts worked well, though oddly only one of the two got significantly more reads than the other, even though I split them intentionally. That split came from a lesson I took from the previous block: trying to pack too much into a single post made them harder to read and harder to write. Breaking it into two kept each post focused on one thing. Long posts don't necessarily mean more value, and there's a real risk that length discourages people from finishing.
What flopped
Success is relative. I try not to fixate on view counts or likes; the benchmark I keep coming back to is whether the content would have been useful to me earlier in my career. Where I may have misjudged this week is the technical depth. Some of this material might be too specific for where most of the audience (ArtStation). Interesting content, possibly on the wrong platform for some of it.
Into next week
Block 4: math and code. This is the stretch I've been building toward. The posts so far have referenced the underlying math without going into it properly. Next week that is going to change, hopefully.
© 2026 Stefan Groenewoud. All views are my own, not those of my employer.