Comment by Agentlien

I looked up your blog and it is clear you have a deep interest for explaining ideas and programming techniques. That's great, there's passion! I even found that you've written about some things close to my own heart:

https://www.makonea.com/en-US/blog/Pokemon-Red-and-the-Evolu...

Looking through it I learned some cool stuff - I had no idea about this.

However, there's one piece of advice which seems applicable to most technical writing I saw on this blog, especially the Pokémon FSM one:

You need to work on pacing and length. The core issue is very broad scope. Think carefully about your target audience and the key insight you want to communicate. Then narrow your scope to communicating only what is necessary for that idea, skipping things your target audience can be assumed to already understand. The writing will automatically get snappier and more engaging.

If you want to explain the FSM script engine in Pokémon you have to assume the reader is somewhat familiar with programming and won't need a primer on registers. Otherwise you're writing a low-level programming primer, not an article about a clever technique in a video game.