The screenshots were definitely taken near the end of the project, while I still had it all in my head but before I started writing. In general, the process lo

The screenshots were definitely taken near the end of the project, while I still had it all in my head but before I started writing. In general, the process looked like: - Brainstorm and reverse engineer first. Have in the back of my mind that I'm writing this up, and releasing a tool, at the end. This guides my search: no your reader won't want to desolder something to use their camera, so yes you need to speak the stock Baichuan protocol. - As I hit interesting things (like the Charlie Scrambler) start filling out a Google Keep note with keywords that will remind me of them when I'm writing. - Take screenshots and produce other media, giving me a rough layout of waypoints that the article has to hit. - Write the article, editorializing optional but recommended. For me, my "writing mindset" is very different from my "engineering mindset." Some days, I can pound out a new piece of code and sometimes it will even be a decent design. Other days, I can write clear documentation. Very seldom can I do both on the same day.