
software engineer @bloomberg | cs + engineering
London, UK
Joined August 2017
- Tweets5.9K
- Following721
- Followers6.1K
- Likes10.9K
wow!
The Lean FRO and Mathlib Initiative have released a joint statement on the Lean verification of the Riemann Hypothesis.
On November 20, Levent Alpöge released a proof of the Riemann Hypothesis as a Lean library of 17 million lines of code. Over the past day, the Lean and Mathlib communities worked together to verify it. The statement certifies the proof as correct and describes how it meets all necessary verification criteria.
Congratulations to Levent on this achievement, and thank you to everyone in the community who contributed to the verification.
Full statement: leanprover-community.github.…
1
232
I M Y K E retweeted
“If you have a 10% chance of a 100x return, you should take that bet every time.”
— Jeff Bezos
i think before you shard you have to consider your use cases: “what operations should be possible without leaving a shard?” and “what are the most important queries and access patterns?”
related data that is frequently accessed or modified together should ideally be on the same shard. for instance, if an application is heavily centered around user relationships, you could use user_id as the shard/partition key so that data belonging to a particular user is on the same shard/partition.
if the application still has use cases that require querying data across multiple shards, one approach is to just denormalize the data.
Replying to @TayCode
And on sharding, this is another place Mongo makes sense.
Sharding relational data is not just “split the rows across servers”. You now have to worry about foreign keys, constraints, migrations, joins and transactions across shards.
What happens when data on shard B points to data on shard A? What if a new shard misses a migration? What if related data gets split across shards?
With Mongo, the data is usually self-contained documents. Pick a good shard key, keep related data together, and you remove a lot of that cross-shard headache entirely.
That’s a much cleaner model for data you already know will need to scale horizontally.



















