CODE

Writing about the bleeps and the bloops

Not actually a devlog #10

Hey! Still not much concerning the side-projects so here are the articles! Have a good read!

Reads 📖

  • 🇬🇧 30 Fundamental Techniques for Software Architects. Sharing vision and strategy when creating (or refactoring) a new architecture is not simplest thing to do. It's especially hard when many actors are involved and having multiple frameworks to be understood by specific audiences is critical. In this article you have a plethora of choices to do to so.
  • 🇬🇧 Top 5 Communication Frameworks for Engineers You Must Remember. Like the one before having the best toolset to communicate is crucial, here you'll have ways to oganizare how you communicate and orchestrate your thoughts when presenting.
  • 🇬🇧 Collaboration sucks. I've always tried to promote democracy and open room thinking when trying to create. And I've started working in a bigger team (like x4 times bigger). It was hard to move forward and a bit frustrating. Then I got to orchestrate the choices, well yeah collaboration sucks AND that's exactly when you understand that "divide and conquer" is not necessarily bad. Giving less ownership to the whole team and delegate to people capable to have a better expertise (or can learn to get it) is like unlock a superpower.
  • 🇬🇧 Invert, always invert. I loved the way this article presents a simple technique to totally change POVs about challenges. Will try.
  • 🇬🇧 To get better at technical writing, lower your expectations. A good reminder to keep the things simple, even when you think they should be complex, especially when you think they are complex.