Architecture Weekly #100 - 7th November 2022
Welcome to the new week!
🎉 🕺 It’s the 100th edition! Boy, that escalated quickly!
I started Architecture Weekly with the idea to organise links and save them from disappearing when my browser crashed. Now it got much bigger than that. Two years later, it has over 1700 subscribers in total. It also has an exclusive community of 49 paid subscribers! We’re having webinars and exchanging ideas. It’s a community where you can safely ask for feedback and constructive criticism. Happy times! Thank you for being here!
Today I’ll do a Live Q&A and answer questions I got through the form and those that’ll be asked live on the Youtube chat. It’s starting at 4 PM Central European Time. Come on in, and take your friends with you!
Yesterday I wrote an article to explain the benefits of Event Sourcing for your business. I aimed it to be understandable for C-Level people (CEO, CTO, etc.). I strongly believe that Event Sourcing can be a huge deal breaker and give your project a competitive advantage. Read more in:
I’m also trying to convey that writing simple code using boring technologies is much better than writing sophisticated, layered code. Unfortunately, most of the examples showing Clean Architecture and Hexagonal Architecture show that this is the model way. Abstraction on top of abstraction, on top of yet another abstraction.
Abstractions are okay if they help to understand the solution, not obfuscate it. Still, writing simple code is not easy. It requires multiple iterations and effort. Telling someone: just write simple code is not real advice. Read more:
Accidental complexity can be a showstopper for projects. Too often, we’re trying to techaround problems that should be solved by design. Throughout my career and projects, I’ve been helping; I saw that in many event-driven architectures. That’s why it’s important to back to basics and do a sanity check if what we’re doing makes sense, see more in:
Seeing what’s happening on Twitter right now got me tripping. Massive layoffs, working extreme overtime without a specific reason. Even sleeping in the office. I was never a fan of Elon Musk and now I’m even less. I’m the type of person, that can’t dissect the person from their works. Some people can, but I cannot. Seeing his behaviour and how he treats people “just because he can” is staggering.
The other aspect is the self-respect and grind culture. We’re privileged to work in the rare industry in which it’s hard to be unemployed. And silicon valley is in the centre of that golden age. I cannot understand why grown-up people are letting to be treated like that. People respect yourselves; it doesn't have to be toxic at work. We need to stop this grind culture. I wrote about it in my recent article. Staying in a toxic environment for a long time leaves scars that might not ever heal. It changes your mind, and it takes years to recover (if you ever manage). I understand exceptional situations when someone is in a complicated situation and needs to delay moving, but still, that should be the priority. In our industry, it's easy to find a new job. Maybe with a worse tech stack, maybe less paid, but at least with a healthier environment. That's much more important. Ultimately, it's just a job; life is somewhere else. Read more:
Check also other links!
p.s. Ukraine is still under brutal Russian invasion. A lot of Ukrainian people are hurt, without shelter and need help. You can help in various ways, for instance, directly helping refugees, spreading awareness, and putting pressure on your local government or companies. You can also support Ukraine by donating, e.g. to Red Cross, the Ukraine humanitarian organisation. You may also consider joining Tech for Ukraine initiative.
Architecture Weekly is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.