CODE

Writing about the bleeps and the bloops

Not actually a devlog #9

Hey! The sneezing season is here! I had a lot on my plate at work and really less time to continue all the side-projects (yeah sure...). Anyway here are some articles!

Reads 📖

  • 🇬🇧 Implementing an Undo/Redo System in a Complex Visual Application. Creating state machines especially in the context of UI applications is always something I've liked. When it comes to play with the history of the actions that's always where I thrive even if it can be hard. This article is talking about the undo/redo couple and it goes quite deep in the implications of such a "simple" feature.
  • 🇬🇧 The Software Engineer Spectrum: Speed vs. Accuracy. All the article is kinda obivous to whoever is working in the tech industry and have navigated between smaller and bigger companies. However I find it really useful to write it somewhere, maybe even everywhere. It's so obvious it could be misregarded by some engineers or managers. I love this article format which is quite straight to the point.
  • 🇬🇧 Rust in Android: move fast and fix things . I'm bit frustrated to share Google articles when it comes to Rust because I love the language and the whole "true" opensourceness feeling we have in this community which sounds less and less (if it ever) Google. I think that's also why I like this kind of articles where a big player is injecting more and more of Rust in their codebase and promote the benefits you can grab from it.
  • 🇬🇧 Every Caching Strategy Explained in 5 Minutes. Caching is hard, knowing how to name caching is also hard (pun intended). Here you'll have a quick article where you have names and the related caching strategies so you'll throw the right terms to the next architecture decision meeting.
  • 🇬🇧 Become the Consequence. This one is a must read. Once again it's exploring how a "manager" or a tech lead has to handle the dreadful duality of quality vs shipping in growing teams. It resonates so well with my current challenges it breaks my brain for a while. Go read it.