guys, please sign this and share

https://chng.it/5b9YpzX6CQ

SQL Studio got a random burst of new traffic and we just reached 2k stars, 2015 stars to be exact.

🎉🎉🎉

TS peeps on twitter have just discovered result types, better late than never i guess.

Here is an npm library i published 3 years ago.

https://github.com/frectonz/optionem

Permutation City

The postgres peeps have started spending some money on marketing.

https://mccue.dev/pages/8-16-24-just-use-postgres

One of the great things about reading scifi stories is that most of the time when people talk about some futurstic invention, you would just say like it's like the thing from this story by this author.

Effective way to get instant street creds.

The worst thing a country could discover is untapped natural resources.

Is this a good book to learn about the concept of microservices?

I am halfway in the first chapter. The concepts are introduced with in each iterative step of a system being built. It reads like a case study.

I like the style of this book but are there better books out there?

So what I gather is that microservices are a way of combating against technical debt.

Any system of sufficient size and sufficient age will inevitably accumulate technical debt, this makes it harder to change that system to add new functionality or modify existing behavior. Technical debt is like a cancer, an un-escapeable by product of age and growth.

Microservices embrace this problem and try to limit these technical debts into their own corner of complexity. So it doesn’t matter that any single microservice is full of technical debt, because when you want to add new functionality or modify existing behavior you will always be adding new microservices to accomplish that goal.

This property allows you to build complex systems without falling down the well of refactors. The only requirement for the existing microservices is that they are functional.

The author of this book calls this idea additivity, but it's just the functional programming idea of composition applied at the service level.

DHH doesn't know about transport independence.

This is presented as a bad thing but I actually want to build systems so complex that it's impossible to explain their behavior.

all ideas are bad/dumb stop analyzing just take a chance

fireship made a video about nix
we're finally mainstream baby 😁

https://youtu.be/FJVFXsNzYZQ