Atomic clock by Ciro Santilli 40 Updated 2025-07-16
Video 1.
How an atomic clock works, and its use in the global positioning system (GPS) by EngineerGuy (2012)
Source. Shows how conceptually an atomic clock is based on a feedback loop of two hyperfine structure states of caesium atoms (non-radioactive caesium-133 as clarified by the Wikipedia page). Like a quartz clock, it also relies on the piezoelectricity of quartz, but unlike the quartz clock, the quartz is not shaped like a tuning fork, and has a much larger resonating frequency of about 7 MHz. The feedback is completed by producing photons that resonate at the right frequency to excite the caesium.
Video 2.
Inside the HP 5061A Cesium Clock by CuriousMarc (2020)
Source.
A similar model was used in the Hafele-Keating experiment to test special relativity on two planes flying in opposite directions. Miniaturization was key.
Contains a disposable tube with 6g of Caesium. You boil it, so when it runs out, you change the tube, 40k USD. Their tube is made by Agilent Technologies, so a replacement since that opened in 1999, and the original machine is from the 60s.
Detection is done with an electron multiplier.
youtu.be/eOti3kKWX-c?t=1166 They compare it with their 100 dollar GPS disciplined oscillator, since GPS satellites have atomic clocks in them.
Video 3. Source. Their super accurate setup first does laser cooling on the caesium atoms.
Gas chromatography by Ciro Santilli 40 Updated 2025-07-16
This technique is crazy! It allows to both:
  • separate gaseous mixtures
  • identify gaseous compounds
You actually see discrete peaks at different minute counts on the other end.
It is based on how much the gas interacts with the column.
Detection is usually done burning the sample to ionize it when it comes out, and then you measure the current produced.
The procedure remind you a bit of gel electrophoresis, except that it is in gaseous phase.
Video 2.
How I invented the electron capture detector interview with James Lovelock by Web of Stories (2001)
Source. He mentions how scientists had to make their own tools during the 40s/60s. Then how gas chromatography was invented at the National Institute for Medical Research and gained a Nobel Prize. Lovelock came in improving the detection part of things.
Of course, "Ciro Santilli" with quotes, since all of those are either taken directly from others, or had been previously formulated by others.
Some anecdotes.
Ciro Santilli never splits up functions unless there is more than one calling point. If you split early, the chances that the interface will be wrong are huge, and a much larger refactoring follows.
If you just want to separate variables, just use a scope e.g.:
int cross_block_var;

// First step.
{
    int myvar;
}

// Second step.
{
    int myvar;
}
Ciro has seen and had to deal with in his lifetime with two projects that had like 3 to 10 git separate Git repositories, all created and maintained by the same small group of developers of the same organization, even though one could not build without the other. Keeping everything in sync was Hell! Why not just have three directories inside a single repository with a single source of truth?
Another important case: Linux should have at least a C standard library, init system, and shell in-tree, like BSD Operating Systems, as mentioned at: Section "Linux".
Whenever someone asks:
I can only see this one thing different our setups, do you think it could be the cause of our different behaviour?
you don't need to read anymore, just point them to this page immediately. Virtualization for the win.
Sun Erniang by Ciro Santilli 40 Updated 2025-07-16
Erniang is way more popular than her ranking in the 108 Stars of Destiny.
This is of course in part because she is one of the only 3 108 Stars of Destiny women. But her story about making human mantou is particularly fun!
She's also quite seductive, which gives directors a good opportunity for a bit of fan service. See e.g. kknews.cc/history/6epp2pp.html for a still from The Water Margin showing some good cleavage for example.
Sometimes you are really certain that something is a required substep for another thing that is coming right afterwards.
When things are this concrete, fine, just do the substep.
But you have to always beware of cases where "I'm sure this will be needed at some unspecified point in the future", because such points tends to never happen.
YAGNI is so fundamental, there are several closely related concepts to it:
Figure 1.
xkcd 2730: Code Lifespan
. Source.

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!
We have two killer features:
  1. 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-calculus
    Articles 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/derivative
  2. 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.
    Figure 2.
    You can publish local OurBigBook lightweight markup files to either https://OurBigBook.com or as a static website
    .
    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.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
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