Architecture Weekly #87 - 8th August 2022
Welcome to the new week!
Do you want to expose your company to a wide range of developers? One of the best ways to get social proof is to support Open Source. I'm thinking about an intriguing idea that could be an excellent option for you to build positive recognition!
Event Sourcing is a great way to connect the business and developers. It enables collaboration and mutual understanding of the business process and implementation. InfoQ, in their trends report, the "Late Majority" already uses it. I think that's a bit too early to say that, but that's also a chance for you!
Recently, I open-sourced spin-off of my private Event Sourcing workshops: self-paced kits. They're not the same experience as full workshops, but I think they're a decent and unique starting point that significantly cuts the ramp-up phase. They enable developers to learn the foundations of this pattern.
So what's the deal? I'm getting many questions about versions in the different technology stacks: Go, TypeScript, Rust, PHP, you name it! I'd like to deliver it, but there's an issue. I only show what I feel comfortable with. I want to do it in an idiomatic way and at the same level as I already did.
That's the chance for you! We could join our forces. Like Tom Cruise said in Jerry Maguire: "help me, help you". If your company would like to sponsor my effort of delivering the new version of those learning kits, I can use my channels (blogs, repositories, architecture weekly) to share that and ensure that the message reaches the audience.
Feel free to reach me in the comments or by direct message. I think that we can find a way to build the proper synergy!
As sharing is caring, even if that's not the offer for you or your company, I'll appreciate resharing or just sending the feedback in the comments confirming that you'll be interested as a developer in having such a self-paced kit!
In my recent article last week, I closed a trilogy about composition in business modelling. I explained how TypeScript enables straightforward and concise modelling. I showed how to build a simple but fully working WebAPI using Event Sourcing and ExpressJS with a domain modelled in TypeScript. See Straightforward Event Sourcing with TypeScript and NodeJS.
The critical aspect of proper modelling is setting proper boundaries. There are different dimensions: autonomy, change impact, language and context, etc. Check Trond Hjorteland’s talk Good Fences Make Good Neighbours, where he explains various aspects.
I like, from time to time check whitepapers. Some of them are indeed not easy to read, filled with jargon. Yet, a lot of them are the opposite. Well-written, touching, in-depth topics that are typically not covered in blog articles. I have two of them this week:
One explains the design of the AWS key-value database DynamoDB. The other shows intriguing dynamics and impact of the team composition.
Team composition needs to take a lot of aspects. Skills are only one aspect of that. Too often, a less competent technical team can be much more performant than a team containing technical experts. Why? Check:
Check also other links!
p.s. I invite you to join the paid version of Architecture Weekly. It already contains the exclusive Discord channel for subscribers (and my GitHub sponsors), monthly webinars, etc. It is a vibrant space for knowledge sharing. Don’t wait to be a part of it!
p.s.2. 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.