I think there is a more important reason to blog besides the 3 reasons listed: to force yourself to slow down, organize your thoughts, fill in the holes, and articulate your points.
That's what I was trying to cover with the "make your newly-acquired knowledge concrete" bit, and was my focus in the previous post. This time around I wanted to look into the aspects that might be impacted by AI (and why I didn't think they would be).
Did you make SageMath? I used it a bunch in college. It was/is such a cool tool. There was a LaTeX plugin or something and I used it to grade students papers. It's also how I learned about hardware and software precision. Along with a whole bunch of other stuff.
Also very much thought it was cool to know someone can nerd out on math and skateboard.
You might be surprised how many people read your blog! If you hang out in techie places, you might even get some, "oh, I read your blog!", comments from strangers.
I ran a study at Microsoft years ago that’s relevant to this. Can I inject static analysis warnings into code reviews? How many? Which ones? What about nearby unchanged code?