CODE

Writing about the bleeps and the bloops

Devlog #2

Hey! Not much to show today, as planned nothing moved on my personal projects side 😅. However some great news and reads from the outside internets! First things first FOSDEM Devrooms have been announced and I should go back to this edition \o/.

Reads 📖

  • Bye Bye Google. A great story (in French) about the erg, a belgian school of arts and how they free themselves from Google Accounts system.
  • Paying down tech debt: further learnings. I love reading about tech debt. It's a critical tool we have as developers (and product teams) to leverage legacy technologies (or choices) without compromising too much with newer techs (or specs changes). It's also a pragmatic way to have an empirical history of architecture decisions and could even help us to look back to the past when trying to understand product delivery rythm. Long story short, this article is a great read and you may want to read it if you any interest about the subject.
  • Basic Things. An older one about what a project should implement or provide at the most basic level especially for bigger projects.
  • Why is language documentation still so terrible?. A rant about language documentations and what they should look like. Not sure about the author tone but I totally share their opinion about Rust documentation. I would add even if Java "official" documentation is a mess, Kotlin is quite pleasant to browse!