LLMs have made a lot of work easier for the present. A lot of shared knowledge acquired over platforms like stackoverflow enabled the LLMs. But now that more people rely on LLMs and no longer continue building those shared knowledge bases, will it hurt the future?
October 13, 2025 at 10:49 AM
LLMs have made a lot of work easier for the present. A lot of shared knowledge acquired over platforms like stackoverflow enabled the LLMs. But now that more people rely on LLMs and no longer continue building those shared knowledge bases, will it hurt the future?
Reposted by Sid
An unordered / non-exhaustive list of things that helped scale Bluesky's infra efficiently:
+ Exiting the cloud (colocation)
+ HAProxy w/many Node backends
+ Go w/clever code
+ ScyllaDB
+ SQLite w/per user databases
+ Redis w/many instances
+ AMD servers w/many cores
+ Purchasing bandwidth directly
+ Exiting the cloud (colocation)
+ HAProxy w/many Node backends
+ Go w/clever code
+ ScyllaDB
+ SQLite w/per user databases
+ Redis w/many instances
+ AMD servers w/many cores
+ Purchasing bandwidth directly
November 11, 2024 at 3:54 AM
An unordered / non-exhaustive list of things that helped scale Bluesky's infra efficiently:
+ Exiting the cloud (colocation)
+ HAProxy w/many Node backends
+ Go w/clever code
+ ScyllaDB
+ SQLite w/per user databases
+ Redis w/many instances
+ AMD servers w/many cores
+ Purchasing bandwidth directly
+ Exiting the cloud (colocation)
+ HAProxy w/many Node backends
+ Go w/clever code
+ ScyllaDB
+ SQLite w/per user databases
+ Redis w/many instances
+ AMD servers w/many cores
+ Purchasing bandwidth directly
Really loved this exchange. It’s inspiring to see how alternative perspectives/opinions were encouraged out of genuine curiosity to understand how ATProto could be improved and the respectful exchange of ideas.
Looking forward to the reply-reply.
Looking forward to the reply-reply.
The incredibly wonderful @bnewbold.net, who encouraged me to write up my "How decentralized is Bluesky, really?" blogpost, wrote up his response: whtwnd.com/bnewbold.net...
I'm reading it now. I'll spend some time mulling it over before I make my "reply-reply" but maybe you should read it too!
I'm reading it now. I'll spend some time mulling it over before I make my "reply-reply" but maybe you should read it too!
Reply on Bluesky and Decentralization | bryan newbold
This is a reply to Christine Lemmer-Webber's thoughtful (and widely read) "How decentralized is Bluesky really?" blog post.
I am so happy and grateful that Christine took the time to write up her tho...
whtwnd.com
November 28, 2024 at 5:31 PM
Really loved this exchange. It’s inspiring to see how alternative perspectives/opinions were encouraged out of genuine curiosity to understand how ATProto could be improved and the respectful exchange of ideas.
Looking forward to the reply-reply.
Looking forward to the reply-reply.
Reposted by Sid
Functional Programming self-affirmations:
1. Parse, Don’t Validate
2. Make Illegal States Unrepresentable
3. Errors as values
4. Functional Core, Imperative Shell
5. Smart Constructor
Repeat daily in front of a mirror for 2 minutes.
1. Parse, Don’t Validate
2. Make Illegal States Unrepresentable
3. Errors as values
4. Functional Core, Imperative Shell
5. Smart Constructor
Repeat daily in front of a mirror for 2 minutes.
November 22, 2024 at 11:33 AM
Functional Programming self-affirmations:
1. Parse, Don’t Validate
2. Make Illegal States Unrepresentable
3. Errors as values
4. Functional Core, Imperative Shell
5. Smart Constructor
Repeat daily in front of a mirror for 2 minutes.
1. Parse, Don’t Validate
2. Make Illegal States Unrepresentable
3. Errors as values
4. Functional Core, Imperative Shell
5. Smart Constructor
Repeat daily in front of a mirror for 2 minutes.