It has been a while since my last real “recap.” Originally, I had planned to do these every week, but other things (positive ones) have taken my time completely since. I have not been able to keep the weekly tact, which will probably remain this way in the foreseeable future. Sometimes you may not hear from me for a few weeks; other times, I might pop up in your inbox a few times a week. That’s why I’d like to propose dropping “Weekly” from the name.
Still fine for you? Great, that’s what I was hoping for.
Now, about those last couple of months. Wow, where do I start from?
First, and dearest to my heart, I am happy to announce my first book's release - "Generative Art in Go." Something I had half-jokingly teased about in November of last year is now a living and breathing product. While I am still polishing some tiny bits, the book is out and available for early readers on Leanpub and Gumroad.
From the original idea in my head, the entire experience until the release draft has been full of learning new things. As my first independent product since leaving my job, it was important that I got the book within the 3-month schedule I had set for myself. The topic of generative art is so broad that it could have easily taken me a year or more to cover even half the topics I wanted to. This would have been a disaster.
Instead, I decided to test the waters one bit at a time. I called it the Minimum Viable Book (or MVB for short) - the equivalent of an MVP in the book world. An MVB offers enough for readers to grasp the subject matter and guide the book's further development with their feedback. Which essentially turns the book into a service, doesn't it? This is a whole new territory I would like to discuss in a separate post. For now, I would like to close the book topic with this summary:
- available as MVB on both Gumroad and Leanpub
- new bonus chapters coming soon
- an entirely new Go book in the making. (What?!? Stay tuned 😉)
Product Development Work
Besides the book writing, I was lucky enough to join a small team that could greatly benefit from my help. We have had lots of fun building an MVP from scratch and should soon be able to disclose it to the general public. I can only hint at the tech stack we're using - Go/PostgreSQL on the back-end and Svelte / Tailwind CSS on the front-end. If you are curious why we chose to build a minimalist CMS in Go over Rails/Phoenix/Diango, please reach out to me.
Finally, the part you have been waiting for. Let's go for some picks:
I have been reading a lot lately about code evolution and robustness over time, and the concept of code half-life popped up in a few of my readings. I think this is the earliest reference I have of this concept.
As always, there are a couple of podcast tips too:
First, the Flashback podcast - a great collection of stories about the origins of hardware and software technology.