I'm all for cool OpenGL stuff, but there are much better examples of novel graphics stuff on places like shadertoy.com or https://experiments.withgoogle.com/chrome?tag=WebGL.
I'm all for cool OpenGL stuff, but there are much better examples of novel graphics stuff on places like shadertoy.com or https://experiments.withgoogle.com/chrome?tag=WebGL.
Here's an example of a blog post I wrote "repackaging" a technique:
http://roy.red/droste-.html#droste
Compare to the code I'd found on ShaderToy:
https://www.shadertoy.com/view/4tlGRn
Is it interesting if you've already spent time on this particular thing? Probably not. But it's meant to be a useful introduction, not a novel work.
Yes, except it's really a copy/paste job from learnopengl.com and other sources. It's actually not a useful introduction since it just parrots stuff that is already available on other sites.
For stuff that's novel, you could always browse through this year's SIGGRAPH papers. http://kesen.realtimerendering.com/sig2017.html
But they also probably weren't entirely satisfied with the documentation they found, ran into some stumbling points that took them too long to resolve, and feel like maybe people could learn from their experiences and avoid those pitfalls.
That's usually my motivation for writing a technical blog post. Sure, you might not be able to phrase it in a more succinct or comprehensible way than the tutorials that you used, but you can at least collate them in one place for others. And if nothing else, the process of putting together a detailed set of instructions to reproduce your efforts definitely helps reinforce your own understanding of the subject matter.
You put "blogs" in quotation marks, but then it kind of sounds like you describe a blog.