Has some good mentions, but often leaves you wanting more details of how certain things happened, especially the early days stuff.
Does however paint a good picture of several notable employees, and non-search projects from the early 2000's including:
- the cook dude
- porn cookie guy
- the unusual IPO process
Paints a very positive picture of the founders. It is likely true. They gave shares generously to early employees. Tried to allow the more general public to buy from IPO, by using a bidding scheme, rather than focusing on the big bankers as was usual.
The introduction mentions that Google is very interested in molecular biology and mining genetics data, much like Ciro Santilli! Can't find external references however...
Two of the most compelling areas that Google and its founders are quietly working on are the promising fields of molecular biology and genetics. Millions of genes in combination with massive amounts of biological and scientific data are an excellent match for the Google search engine, the tremendous database the company has in place, and its immense computing power. Already, Google has downloaded a map of the human genome and is working closely with biologist Dr. Craig Venter and other leaders in genetics on scientific projects that may lead to important breakthroughs in science, medicine, and health. In other words, we may be heading toward a time when people can google their own genes.
The book gives good highlight as to why Google became big: search was just an incredibly computationally intensive task. From very early days, Largey were already making up their own somewhat custom compute systems from very early days, which naturally led into Google custom hardware later on. Google just managed to pull ahead on the reinvest revenue into hardware loop, and no one ever caught them back. This feels more the case than e.g. with Amazon, which notoriously had to buy off dozens of competitors to clear the way.
Cover of The Google Story
. Cool data embedded in the Bitcoin blockchain Nelson-Mandela.jpg by 
Ciro Santilli 40 Updated 2025-07-16
Ciro Santilli 40 Updated 2025-07-16bitfossil.com/78f0e6de0ce007f4dd4a09085e649d7e354f70bc7da06d697b167f353f115b8e/ in block 273536 (2013-12-07).
This is one of the earliest AtomSea & EMBII uploads.
Nelson-Mandela.jpg"There is nothing like returning to a place that remains unchanged to find the ways in which you yourself have altered." - Nelson Mandela Nelson Rolihlahla Mandela was a South African anti-apartheid revolutionary, politician and philanthropist who served as President of South Africa from 1994 to 1999. - Wikipedia Born: July 18, 1918, Mvezo, South Africa Died: December 5, 2013.
Cool data embedded in the Bitcoin blockchain Technically interesting ordinal by Ciro Santilli 40 Updated 2025-07-16
Ciro Santilli 40 Updated 2025-07-16This section is about ordinals that are interesting primarily due to technical reasons linked to edge cases of the protocol.
Interesting MIME types:
- ordinals.com/inscription/dad86d722156b8c384c1f3243e40aa7a0f6f5be496bc24e19485831584f9803fi0: mime type is an UTF-8 orange emoji "🟠"
- ordinals.com/inscription/bc7b86245159cdf8bc63489687909f766a0a0e08279d23fb077cdd60ab1e9f22i0: mime type is an XSS attempt:
<script>alert('xss in content type')</script> tx=bc7b86245159cdf8bc63489687909f766a0a0e08279d23fb077cdd60ab1e9f22 - ordinals.com/inscription/bc7b86245159cdf8bc63489687909f766a0a0e08279d23fb077cdd60ab1e9f22i0: mime type is "FuckYou"
- ordinals.com/inscription/00b0ece72217ce49b637b3f9bf5335bc245e588568aa0676581b40c1bedc521di0: the mime is a long JSON. However, it does appear to be a valid feature as it rendered specially on ordinals.com.
Different
ord markers:- 71e85885522047240a9e70542145dbf2385e1bd468e6ac6002aa755422ea10f5 uses
takingnames. Decode with:gives the PNG of the wireframe draing of a washing machine with transparent background.bitcoin-core.cli decodescript "$(bitcoin-core.cli getrawtransaction 71e85885522047240a9e70542145dbf2385e1bd468e6ac6002aa755422ea10f5 true | jq -r '.vin[0].txinwitness[1]')" | jq -r .asm | sed 's/.* 0 //;s/ OP_ENDIF//;s/ //g' | xxd -r -p > 71e85885522047240a9e70542145dbf2385e1bd468e6ac6002aa755422ea10f5.png
Unfortunately, all software engineers already know the answer to the useful theorems though (except perhaps notably for cryptography), e.g. all programmers obviously know that iehter P != NP or that this is unprovable or some other "for all practical purposes practice P != NP", even though they don't have proof.
And 99% of their time, software engineers are not dealing with mathematically formulatable problems anyways, which is sad.
The only useful "computer science" subset every programmer ever needs to know is:
- for arrays: dynamic array vs linked list
- for associative array: binary search tree vs hash table. See also Heap vs Binary Search Tree (BST). No need to understand the algorithmic details of the hash function, the NSA has already done that for you.
- don't use Bubble sort for sorting
- you can't parse HTML with regular expressions: stackoverflow.com/questions/1732348/regex-match-open-tags-except-xhtml-self-contained-tags/1732454#1732454 because of formal language theory
Funnily, due to the formalization of mathematics, mathematics can be seen as a branch of computer science, just like computer science can be seen as a branch of Mathematics!
"P2FKH" terminology mentioned e.g. at: Data Insertion in Bitcoin's Blockchain by Andrew Sward, Vecna OP_0 and Forrest Stonedahl.
Cryptocurrency with focus on anonymity. Was almost certainly the leading privacy coin since its inception until as of writing in the 2020s.
Ciro Santilli has received and held considerable quantities of Monero, notably 1000 Monero donation. so bias alert.
As mentioned at Section "Are cryptocurrencies useful?", Ciro Santilli believes that anonymity is the most valuable feature that really matters on crypto coins, and therefore if he were to invest in crypto, he would invest in Monero or some other privacy coin.
localmonero.co/knowledge/monero-stealth-addresses?language=en gives an overview of the privacy mechanisms:
- ring signatures, which hide the true output (sender)localmonero.co/knowledge/ring-signatures Gives an overview. Mentions that it is prone to heuristic attacks.Uses a system of decoys, that adds 10 fake possible previous outputs as inputs, in addition to the actual input.So the network only knows/verifies that one of those 11 previous outputs was used, but it does not know which one.TODO so how do you know which previous outputs were spent or not?
- RingCT which hides the amounts.
- stealth addresses, which hides who you send toThis forces receivers to scan try and unlock every single transaction in the chain to see if it is theirs or not.The sender therefore can know when the money is spent, but once again, not to whom it is being sent.
Based on en.wikipedia.org/wiki/CryptoNote and like Satoshi Nakamoto created by under the pseudonym "Nicolas van Saberhagen" www.reddit.com/r/Monero/comments/7v2obe/offering_a_bounty_for_a_video_of_the_speech_by/
Coinbase has actually stayed away from trading it even as of 2019 when Monero was the third largest market capitalization crypto because of fear of regulatory slashback: decrypt.co/36731/heres-why-coinbase-still-hasnt-listed-monero. Although it must be said, the value of privacy crypto is greatly reduced when everyone is trading it on exchanges, which require a passport upload to work.
The prototypical example is the Busy beaver function, which is the easiest example to reach from the halting problem.
Pinned article: Introduction to the OurBigBook Project
Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
Intro to OurBigBook
. Source. We have two killer features:
- topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculusArticles of different users are sorted by upvote within each article page. This feature is a bit like:
- a Wikipedia where each user can have their own version of each article
- a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
Figure 1. Screenshot of the "Derivative" topic page. View it live at: ourbigbook.com/go/topic/derivativeVideo 2. OurBigBook Web topics demo. Source. - local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
- to OurBigBook.com to get awesome multi-user features like topics and likes
- as HTML files to a static website, which you can host yourself for free on many external providers like GitHub Pages, and remain in full control
Figure 3. Visual Studio Code extension installation.
Figure 4. Visual Studio Code extension tree navigation.
Figure 5. Web editor. You can also edit articles on the Web editor without installing anything locally.Video 3. Edit locally and publish demo. Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.Video 4. OurBigBook Visual Studio Code extension editing and navigation demo. Source. 
- Infinitely deep tables of contents:
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact