Most of my writing takes the short form and has been for myself. What I mean by that is I write to help myself better understand a topic or process. While writing, I'm working through my understanding of whatever it is I am writing about. If that is something technical, I may have already worked through a solution, but I want to think back through it and make sure I understand all the edges and boundaries. If I am writing about something process or management related, I am reexamining the idea and saying it aloud to make sure it is rationale.

All of the writing I've done to date has been short form, meaning blog posts and newsletters. I wanted to push myself further. I've always wanted to write a book. Be it technical or science-fiction or documentary. And recently, I decided to give it a try.

In the past year or so, I've been learning the programming language Rust. While doing so I was taking notes. Naturally, I compared Rust to another language I was very fluent in—Ruby. Out of that came a few blog posts. After posting a few, I decided to use them as the basis for a long form book. This will be a challenge. I'm open sourcing it as I write it. Once it's fairly complete, I'll share it more broadly. If you're interested, you can find it here. Feel free to share it with others if you think they'd find it useful. Feel free to ping me if you have any comments or suggestions.

Thanks for reading,

Mike