You conveniently leave out that same Wikipedia article on Microcode says: "The act of writing microcode is often referred to as microprogramming, and the microcode in a specific processor implementation is sometimes termed a microprogram."
It is perfectly okay and ethical for some software engineer to browse your blog post, understand nothing / get confused by your terminology, and say so.
IMHO the onus is on you to present your ideas in a way that makes them understandable for at least experts.
Granted, it's not easy and I don't know what I would have done in your place.
Agreed. And that's why I've pushed 13 revisions since the initial publication (https://github.com/breck7/breckyunits.com/commits/main/micro...) 2 days ago. I'm learning how to better explain this. I think this video is the best attempt yet: https://www.youtube.com/watch?v=e4mJh7TgICE
My suggestion to all in this thread who _feels_ there's something interesting here to record, using Loom or similar, your interactions with these ideas and tools.
I can then read your facial expressions and body language and understand much better how you are not understanding things and improve my explanations. Video is a highbandwidth form of communication. And it takes the exact same amount of time! Less time in fact, because you only need to record your interactions with the tool. You don't need to follow that up with written comments.