Om Malik link-posting on his blog:

David Mills, the creator of Network Time Protocol (NTP), which is fundamental to the functioning of networks. Mills, nicknamed the Internet’s Time Lord by his peers, passed away on January 17 at the age of 85. His contributions to the development and evolution of the Internet are numerous and far-reaching. We are quietly losing a generation that has helped build the network we often take for granted. Source: RIP, Internet’s Time Lord – On my Om

I do deal with NTP protocol from time to time at my job as a solution architect. The fathers (and mothers) of the modern computing era are dying.

Avoiding Vendors Lock-in

The notion of “avoiding vendors lock-in” in information technology is interesting. I would argue that it’s impossible to completely be without some sort of vendor lock-in1. At some point, there is always a required commitment level. You commit to open-source software. You commit to a cloud vendor. You commit to a platform. I often give the example of a company building an application internally with a team of developers. In that scenario, the company is committing to something: the application, the data tied to it and its operational model. Applications are hard to replace in many environments. When you decide to invest in software development, you commit to the end product for many years, if not decades, until the organization decides it’s time to transform the application into something else2. There is this concept of “security by design” and of “portable by design,” which should apply to any technical or application architecture. The rest is marketing nonsense.


  1. I do understand data portability concepts and loose coupling principles, though. ↩︎

  2. When it’s time to adopt new architecture paradigms like the cloud is imposing. ↩︎

Confession of the day: I hate being confined to the world of Microsoft 365 for my work, knowing that there are much cooler tools out there. Notion is one example, Basecamp is another one, Monday, etc, even though it might be a controversial opinion. And don’t get me started about the Microsoft Visio; there are dozens of much better alternatives1.


  1. Draw.io, LucidChart, etc. ↩︎

I just realized that I could (and should) use Raycast AI to summarize articles saved into Omnivore and save the summary into the article notes. Then, I could finish up the metadata with appropriate tags. I used to do that within Craft before, but the Craft AI assistant uses GPT 3.5, limits the length of the input into the summarize request and doesn’t support “real tags” like in Omnivore.

So, I made the decision: Bye-bye Write.as👋🏻. It’s fun to move things around on the internet, but I pay the price for being too impulsive and not intentional in some of my decisions. It was an impulsive decision to subscribe to Write.as. There was something seductive in the post editor, and being open source is the way to go. But I have to admit that it was a diversion. Now, focusing on Micro.blog. 😊

Sidenote: I find great satisfaction in simplification. This reminds me of when I was an indie iOS developer: I remember the instants of removing lines of code and making things leaner. It procured a lot of satisfaction.

Quick non-scientific poll: @Manton releases quite a few updates (mostly small1) to Micro.blog during the year and posts the info on @news. Would it be cool if someone created a “What’s New on Micro.blog” series demonstrating these changes and tweaks in action? I know some people prefer to see things in action, not just read a small description. Is there an interest in this?2


  1. I know Manton is working on bigger updates, but they are less frequent and could require a separate video for this. ↩︎

  2. Even without significant interest, I’ll do these videos anyway because I like to create videos for YouTube! 😂 ↩︎

I’m thinking of leaving Write.as. Last year, I purchased a 5-year subscription during a promotion, intending to use it extensively. However, I haven’t used it as much as I anticipated. My main focus was writing about the Ukraine war. I could migrate this to Micro.blog. Yet, I’m concerned that my views on the conflict might offend some people here, as not everyone is interested in politics. 🤔🧐

🌞It’s Sunday, and it’s time for the second edition of the weekly creative summary newsletter! I was late working on this edition and wasn’t sure how it would come out. I’m pretty satisfied with this week’s edition.😀 I’m seeing more and more people heading to the Craft edition of this newsletter, and I’m highly grateful for the interest that this newsletter generates.