CODE

Writing about the bleeps and the bloops

Not actually a devlog #11

Hey! Is that still possible to say "Happy New Year"? If so, let's celebrate it!

Reads 📖

  • 🇬🇧 Architectural Debt is not just Technical Debt. By nature technical debt is not just saying "we don't have the time" or "let's do this later". It's a trade we're doing with our later selves, and it's important to understand the consequences of that trade. It's intracted in many layers of our teams and organizations. This article is exactly about that and help us understand those choices are not just our own.
  • 🇬🇧 Mission, vision, poTAYto, poTAHto. A really nice article about what is mission and vision. It gives us a lot of insights about how to communicate those concepts and how to make them resonate with our audience. And also the scale of each of those concepts.
  • 🇬🇧 Traits of a Good Tech Lead. Becoming a good tech lead is not easy. You need to be conscious of your own limitations and be able to delegate tasks to others who are better suited to handle them. The author tries to give us specific traits to help us differentiate between EM and TL. He also provides a list of behaviors creating confidence for your team and the stakeholders.
  • 🇬🇧 The PERFECT Code Review: How to Reduce Cognitive Load While Improving Quality. Code reviews are fun. Checklists are fun. Acronyms are fun. Go read it.
  • 🇬🇧 Three Ways to Solve Problems. I like the clarity of this article and the straight forward approach. I read it not so long before Why Senior Engineers Let Bad Projects Fail and I find them really complementary.