Vincent Stollenwerk

I‘m fascinated how smart Go‘s time APIs differentiate between telling time using the system clock and measuring durations of time using monotonic clocks. Stumbled upon this in @willemdev.bsky.social‘s great article „time.Now() and the monotonic clock“: www.willem.dev/articles/tim...

Just saw John Ousterhout‘s talk on Software Design. He has some really interesting thoughts. The most important point is probably that he prefers deep classes with small interfaces because they provide the largest amount of abstraction while minimizing additional complexity. youtu.be/bmSAYlu0NcY

For example, why do we have to initiate multiple classes to read data from a file in Java? FileReader, BufferedReader, maybe another one to deserialize the data.

Just saw John Ousterhout‘s talk on Software Design. He has some really interesting thoughts. The most important point is probably that he prefers deep classes with small interfaces because they provide the largest amount of abstraction while minimizing additional complexity. youtu.be/bmSAYlu0NcY

I have a WhatsApp chat where I always receive the 🙂‍↔️ Emoji as 🙂↔. However, when I use it, it‘s rendered just fine. I know that this Emoji is encoded as 🙂, zero-width joiner, and ↔. Additionally, even though it is rendered as it’s separate parts, it’s treated as a single Unicode glyph…

It‘s interesting how so many modern CLI tools are written is Rust. Especially for those, where performance isn’t critical. Is this because the Rust community loves to rewrite stuff in Rust or is Rust actually nice to use for CLI tools? Maybe snappiness also has a subconscious effect on users.

For the last month I‘ve been trying out jj (Jujutsu) as a git alternative. While I didn’t see anything wrong with git before, jj makes complex git operations so simple that I don’t want to go back. Editing history, rebasing, splitting up large commits are all super easy.

Just watched Dan's talk on the AT Protocol. It gives some great insights into the architecture behind Bluesky. Some interesting things that stood out to me:

5. Even if Bluesky, the organization would die, as long as the data is still available on the PDSs, anyone could build an alternative Bluesky client.

Just watched Dan's talk on the AT Protocol. It gives some great insights into the architecture behind Bluesky. Some interesting things that stood out to me:

2. Each PDS host the data of multiple users. These user "repositories" are organized into "collections". 3. Users can grant apps write access to any of these collections. As a result, anyone can write an app with full write access to the Bluesky data.

Just watched Dan's talk on the AT Protocol. It gives some great insights into the architecture behind Bluesky. Some interesting things that stood out to me: