Oskar Dudycz

Pragmatic about programming

Architecture Weekly is 5 years old! 🎉Architecture Weekly 五岁了！🎉

2025-12-29 oskar dudyczSoftware Architecture

Welcome to the new week!欢迎来到新的一周！

Who said that LinkedIn notifications are useless? I did, several times. Yet! Today, I opened my computer for the first time since last Tuesday and just saw a notification that Architecture Weekly is 5 years old now!谁说 LinkedIn 的通知毫无用处？我曾多次这样说过。然而！今天，我自上周二以来第一次打开电脑，就看到了一条通知：Architecture Weekly 现在已经五岁了！

2025 12 29 cover

At this point, you probably know that I’m not the anniversary-type-of-guy (my wife loves that part of me…), but well, that’s a nice milestone!说到这里，你可能已经知道我不是那种热衷于纪念日的人（我妻子很喜欢我这一点……），但话说回来，这确实是一个不错的里程碑！

Architecture Weekly started as a way to organise my readings. I’m a curious guy, and I like to read a lot about different topics. During my career, I worked on a lot of weird projects, which exposed me to many technologies and approaches. It was not always pleasant, but it taught me that technology is a tool, and there’s a big diversity of tools that can lead you to a proper solution.Architecture Weekly 最初是我整理阅读内容的一种方式。我是一个充满好奇心的人，喜欢阅读各种不同主题的内容。在我的职业生涯中，我参与过许多奇奇怪怪的项目，这让我接触到了许多技术和方法。过程并不总是愉快的，但它教会了我：技术只是一种工具，而多样化的工具组合才能引导你找到合适的解决方案。

So, I had always had hundreds of open browser tabs until my Firefox crashed from time to time (yes, I’m a Firefox-type-of-guy). I’m sure you know that too. I tried multiple ways to organise that: tools like Notion, e-mail threads, etc. None of them was perfect. At some point, my friends treated me like a librarian and asked me for interesting links on a topic or what interesting things I’d read recently. I decided to put my readings publicly into a Git repository and use Markdown, so I can easily share them. This repository still exists: https://github.com/oskardudycz/ArchitectureWeekly. At first, just links organised in groups.所以，我曾经总是打开着数百个浏览器标签页，直到 Firefox 不时崩溃（没错，我就是那种用 Firefox 的人）。我相信你也有过同样的经历。我尝试过多种整理方式：像 Notion、电子邮件线程等工具。没有一个是完美的。后来，朋友们把我当成图书管理员，会向我询问某个主题的有趣链接，或者我最近读了什么有意思的东西。我决定将我的阅读内容公开发布在 Git 仓库中并使用 Markdown，这样我就能轻松地分享它们。这个仓库至今仍然存在：https://github.com/oskardudycz/ArchitectureWeekly。起初，它只是按类别整理的链接。

I started sharing it with my friends, and they told me it was useful, so I started sharing it with their friends. It seemed so useful to others that I shared it on the other channels, socials, and groups I was part of. Feedback was still positive, and some people started pushing me to create the newsletter, even though they could subscribe to GitHub release e-mail notifications; they still landed in the same notification swamp, as usual, with other notifications. So they asked if I could set up “a proper newsletter”. I was reluctant to do it, but well, as you already know, I did. I used Substack because it helped me avoid the usual accidental complexity by writing my own blogging engine from scratch.我开始与朋友们分享，他们说这很有用，于是我又开始与他们的朋友分享。它对其他人似乎非常有用，所以我又在自己参与的其他渠道、社交媒体和群组中进行了分享。反馈依然积极，有些人开始催促我创建通讯（newsletter），尽管他们本可以订阅 GitHub 的发布邮件通知；但像往常一样，这些邮件最终还是淹没在与其他通知混杂的通知沼泽中。所以他们问我是否可以建立一个“正式的通讯”。我起初很抗拒，但正如你所知，我还是做了。我使用了 Substack，因为它帮我避免了从零开始编写博客引擎所带来的额外复杂性。

At some point, I decided to try making a paid version of the newsletter. I decided to build a Discord community for paid subscribers and my GitHub Sponsors. I started to also run webinars every month, also inviting guests.后来，我决定尝试制作付费版本的通讯。我决定为付费订阅者和我的 GitHub 赞助者建立一个 Discord 社区。我也开始每月举办网络研讨会，并邀请嘉宾参加。

Complete list of webinars we had so far:我们迄今为止举办的网络研讨会完整列表：

And now, yes, all of them are available for free. You can watch them. It’s around 50 hours of free knowledge. I believe that it is of much better quality than some paid courses. Why did I make them public?现在，没错，所有这些都可以免费观看。总共约 50 小时的免费知识。我相信它们的质量远高于某些付费课程。我为什么要把它们公开？

At some point, I realised that I don’t have much fun with organising those links; it was more of a burden, as curating such lists takes a lot of time. I’m also a perfectionist-type-of-guy, so I wanted to ensure that what I recommend is worth the read. It triggers the movement of brain cells. So if you read the article, you might disagree with it, but at least it’s sparking some thought. I also wanted to synthesise them and put my comments. It may seem like a simple thing to provide such articles. But try to keep it at the proper level week after week, and you’ll see it might not be as easy as it seems.后来我意识到，整理这些链接对我来说乐趣不多；这更像是一种负担，因为策划这样的列表非常耗时。我也是个完美主义者，所以我想确保我推荐的内容值得一读。它能激发大脑细胞的活动。所以如果你读了这篇文章，你可能会不同意它的观点，但至少它能引发一些思考。我也想对它们进行总结并加上我的评论。提供这样的文章看起来可能很简单。但试着每周都保持在适当的水平，你就会发现这并不像看起来那么容易。

There were not enough paid subscribers to justify the time spent on it, even though I was named a Substack Bestseller. Yes, running a newsletter is not a great business plan. There are some exceptions to that, but even if you’re in the top few per cent, then it might not be enough to even justify the time spent on it.付费订阅者不足以证明我投入的时间是合理的，尽管我曾被评为 Substack 畅销作者。是的，运营通讯并不是一个好的商业计划。尽管有一些例外，但即使你处于前几个百分点，可能也不足以证明投入的时间是合理的。

I decided to try a different angle and made Architecture Weekly a fully paid newsletter. Starting with a deep dive into Database Connection Pooling. I tried to see if I could grind for a while, providing high-quality content that’s not available elsewhere. I think I managed to deliver a lot of articles like that, and the paid subscriber count grew, but it was still not enough to justify my work. I enjoyed writing such articles a lot, and I still do, but it has put more pressure on me. And preparing such content takes time and effort. The effort I could spend elsewhere, e.g., with my family, in better-paid work like my workshops and consulting, or in my OSS projects.我决定尝试一个不同的角度，将 Architecture Weekly 做成完全付费的通讯。从深入探讨数据库连接池开始。我试图看看能否坚持一段时间，提供其他地方无法获得的优质内容。我认为我确实发布了很多这样的文章，付费订阅者数量也有所增长，但依然不足以证明我的工作是合理的。我非常喜欢写这样的文章，现在依然如此，但这给我带来了更大的压力。准备这样的内容需要时间和精力。这些精力我本可以花在别处，例如陪伴家人，或者从事报酬更高的工作，如我的研讨会和咨询，或者我的开源项目。

And now, here we are, 10 months later and well, I still delivered a lot of deep dives, but shifted closer to the stuff I do daily, so helping other humans build systems and getting benefit from the Event-Driven approach. As you see, recently I cross-posted articles to my blog and here. I also used the angle of my work on tools like Emmett to explain general concepts.现在，10 个月过去了，我依然输出了许多深度文章，但内容更偏向于我日常所做的事情，即帮助他人构建系统并从事件驱动的方法中获益。如你所见，最近我将文章同时发布在我的博客和这里。我也利用我在 Emmett 等工具上的工作经验来解释通用概念。

What’s next? I’ll probably continue doing it as is; I might also consider merging the blog and newsletter into one. I even own domain event-driven.news, so maybe some rebranding will happen. But it’s not yet decided.接下来是什么？我可能会继续保持现状；我也在考虑将博客和通讯合并为一个。我甚至拥有 event-driven.news 这个域名，所以可能会进行品牌重塑。但目前还没决定。

I’ll definitely continue sharing what I learned, blogging, but the exact form? We’ll see. I’m open to suggestions! Comment under this post and tell me your thoughts.我肯定会继续分享我所学到的东西，继续写博客，但具体形式如何？我们走着瞧。欢迎提出建议！在这篇文章下评论，告诉我你的想法。

What type of content would you like to see here? Or is there some that you’d be even open to paying for?你希望在这里看到什么类型的内容？或者有什么内容是你愿意付费阅读的？

Can’t promise that I’ll deliver all of them, but it’ll give me a food for thought.不敢保证我都能做到，但这会为我提供一些思考。

Nevertheless, it’s time for a small celebration!无论如何，是时候进行小小的庆祝了！

Thanks for being here with me through this journey!感谢你在这一旅程中与我同行！

Cheers!干杯！

OskarOskar