Better Dev Link

A study of every high severity production incident at Microsoft Azure services over a span of six months, where the root cause of that incident was a software bug. Data-format bugs, fault-related bugs, timing bugs, and constant_value bugs being the largest categories

Uncle Bob, author of Agile method, discuss about class vs data structure since we used them to encapsulate data.

Highly opininated on some discuss about usage of Kafka and its hype among big corp.

Love or hate it. You have to write JavaScript and use devtool to debug it. Slack write up on using Chrome Tracing: a tool that’s built into Chrome (and Electron) that can collect a huge variety of detailed performance data.

Lessons learned migrating RevenueCat from RDS PostgreSQL to Amazon Aurora. I like how they said it: “Be opportunistic. Do it when you can do it, before you must do it.”

How using explicit state machines in the modelization and implementation of user interfaces leads to robust, maintainable and testable interfaces.

CAP says that distributed system cannot sasitify all three of Consistency, Availability and Partition tolerance. What if we were to squint and apply the CAP theorem to another distributed system: a team of software engineers working towards a common goal

We all love Redis. It is easy to setup and run and you just forgot about its exsistence. But its single thread make you have to carefuly to avoid blocking in a single request. KeyDB is a multi-thread fork of Redis. It claims 2x performance.

We linked to this serias a few times. In this post, we’ll extend the ulisp compiler’s LLVM backend to support printing integers to stdout.

A collaborative editor are able to keep a consistent state, even though multiple users are typing simultaneously. Even if multiple users are hammering away, smashing their keyboards, the state is kept consistent. Operational Transformation and Conflict-Free Replicated data type are algorithms to solve this problem.