This is the most convincing case i have seen about the identity of Satoshi Nakamoto. I kinda believe it.
https://evanhatch.medium.com/len-sassaman-and-satoshi-e483c85c2b10
https://evanhatch.medium.com/len-sassaman-and-satoshi-e483c85c2b10
Medium
Len Sassaman and Satoshi: a Cypherpunk History
Weβve lost far too many hackers to suicide. What if Satoshi was one of them?
π«‘2π³1
Forwarded from Beka (Beka)
Change.org
Sign the Petition
Justice for Heaven and her mother
This media is not supported in your browser
VIEW IN TELEGRAM
SQL Studio got a random burst of new traffic and we just reached 2k stars, 2015 stars to be exact.
πππ
πππ
π34π₯2
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
Here is an npm library i published 3 years ago.
https://github.com/frectonz/optionem
GitHub
GitHub - frectonz/optionem: A library for people with options and results.
A library for people with options and results. Contribute to frectonz/optionem development by creating an account on GitHub.
The postgres peeps have started spending some money on marketing.
https://mccue.dev/pages/8-16-24-just-use-postgres
https://mccue.dev/pages/8-16-24-just-use-postgres
Forwarded from will to code
I updated Telegram forms over the weekend. I scraped the spaghetti hackathon codebase and remade the whole thing with shadcn. Also added some new features.
βοΈ Users can now generate or upload their own image for form card (This took forever)
βοΈ Data table view for responses
βοΈ New logo
Getting closer and closer to V 1.0
But in classic fashion I have to abandon this for sometime and go work on something else.
New GitHub
@Formfortelegrambot
βοΈ Users can now generate or upload their own image for form card (This took forever)
βοΈ Data table view for responses
βοΈ New logo
Getting closer and closer to V 1.0
But in classic fashion I have to abandon this for sometime and go work on something else.
New GitHub
@Formfortelegrambot
π₯8
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.
Effective way to get instant street creds.
π19
The worst thing a country could discover is untapped natural resources.
π4π―2
Frectonz
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β¦
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.
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.
π3