Bibliography:
- maths-people.anu.edu.au/~andrews/DG/ Lectures on Differential Geometry by Ben Andrews
Nice result on Lebesgue measurable required for uniqueness.
How to blackout your window without drilling by 
Ciro Santilli 35 Updated 2025-03-28 +Created 1970-01-01
Ciro Santilli 35 Updated 2025-03-28 +Created 1970-01-01This is meant to be an answer to: diy.stackexchange.com/questions/27669/how-can-i-thoroughly-blackout-a-bedroom-window-on-a-budget but that question was protected and I can't answer right now because I don't have 10 reputation on the website, so here goes.
Questions for Ciro Santilli's future self by Ciro Santilli 35 Updated 2025-03-28 +Created 1970-01-01
Ciro Santilli 35 Updated 2025-03-28 +Created 1970-01-01Future self, answer these.
10 years:
- 2017-2027: did self-driving cars become big?
- 2017-2027: did virtual reality become big?
20 years
- 2018-2038: are companies offering free full genome decoding just to get your genomic data and sell it to pharma companies?Someone like Ciro then creates an open source genomic database funded by health organizations that publishes genomes + phenotypes anonymously. Genome to phenotype analytics go crazy big.
40 years:
- 2017-2057: was human level AI reached (by non-bio devices :-)), even if very slow?
- 2017-2057: did China become democratic?
- 2018-2058: did impressive brain-computer interfaces show up?
Why Ciro Santilli removed Disqus comments from his website in 2019-05-04 by Ciro Santilli 35 Updated 2025-03-28 +Created 1970-01-01
Ciro Santilli 35 Updated 2025-03-28 +Created 1970-01-01Commit: github.com/cirosantilli/cirosantilli.github.io/commit/794705a201a79b5128934e69df85e3511655c03f
As Ciro started getting a lot of comments on his home page about China, he decided that Disqus does not scale, and that it would be more productive long term to remove it and point people to GitHub issues instead.
Upsides of removal:
- Disqus discoverability is bad:
- there is no decent way to search existing issues, you have to do JavaScript infinite loading + Ctrl + F. So every reply that he wrote is a waste of time, as it will never be seen again.
- comments don't have: decent URLs, titles, metadata like tags or open / close
- Disqus archival is bad: web.archive.org/ does not work, and no one knows how to export the issues: www.archiveteam.org/index.php?title=Disqus
- before, there were two places where people could comment, Disqus and GitHub issues. Now there is just one.
- Disqus has ads if you ever reach enough traffic, which unacceptable, especially if the website owner don't get paid for them! It also makes page loads slower, although that likely does not matter much.
Downsides:
- people are more likely to comment on Disqus than to create an issue on GitHub, especially because most people use GitHub professionally. But this has the upside that there will be less shitposts as well.
- with Disqus you can see all issues attached to a page automatically, which is nice. But for as long as Ciro is alive, he intends to just solve the issues, cross link between content and issues and tag things appropriately.
Ciro's stance towards China hasn't changed, and China comments and corrections about his website are still welcome as always.
Related issue: github.com/cirosantilli/cirosantilli.github.io/issues/37
Media rationale of Ciro Santilli's website by Ciro Santilli 35 Updated 2025-03-28 +Created 1970-01-01
Ciro Santilli 35 Updated 2025-03-28 +Created 1970-01-01 Ciro Santilli's documentation superpowers by Ciro Santilli 35 Updated 2025-03-28 +Created 1970-01-01
Ciro Santilli 35 Updated 2025-03-28 +Created 1970-01-01Ciro Santilli has the power to document stuff in a way that makes using them awesome, as evidenced by his his Stack Overflow contributions (notably those in the best articles by Ciro Santillis), and other online contributions.
If your project does something awesome, hiring Ciro means that more people will be able to notice that it is actually awesome, and use it.
He likes to do this in parallel to contributing new features, quickly switching between his "developer" and "technical documentor" hats.
This means of course that he will develop new features a bit slower than others, but he feel it is more valuable if end users can actually use your project in the first place.
His technique is to provide upfront extremely interactive and reproducible getting started setups that immediately show the key value of the project to users.
He backs those setups with:A prime example of kind of setup is Ciro's Linux Kernel Module Cheat.
- scripts that automate the setup much as possible to make things enjoyable and reproducible
- a detailed description of the environment in which he tested: which OS, version of key software, etc.
- a detailed description of what is expected to happen when you take an action, including known bugs with links to bug reports
- theory and rationale on the sections after the initial getting started, but always finely interspersed with concrete examples
- all docs contained in a Git-tracked repo, with the ability to render to a single HTML with one TOC
- short sentences and paragraphs, interspersed with many headers, lists and code blocks
While he create this setup, he inevitably start to notice and fix:
- bugs
- annoyances on the public interface of the project
- the devs were using 50 different local scripts to do similar things, all of them semi-broken and limited. Every new hire was copying one of those local scripts, and hacking it up further.
- your crappy build / test / version control setup
Exploiting this skill, however, requires you to trust him.
When he tells to managers that he's good at documenting, they always say: great, we need better documentation! But then, one of the following may happen:
- managers forget that they wanted good documentation and just tell him to code new features as fast as possible
- they don't let him own the getting started page, but rather and expect him to try and fix the existing crappy unfixable existing getting started, without stepping on anyone's pride in the process >:-)This makes him tired, and less likely to do a good job.Good documentation requires a large number of small iterative reviews, and detailed review of every line is not always feasible.Too many cooks.
Ciro's passion for documentation and tooling has the effect that if you have crappy documentation and tooling and don't want them to be fixed, Ciro will end up trying to fix those tools instead of doing what you tell him to do anyways, which might lead to him quitting because he can't stand the tools, or you firing him because he's not doing the job you think I should be doing. So please, don't bother hiring Ciro if you have crappy documentation and tooling.
Psychological analysis of why Ciro has this gift: How Ciro Santilli manages to write so much.
Ciro often has the following metaphor in his mind:
New discoveries are like very rough trails where you have to cut through heavy bushes (an original research paper).After a brave explorer goes through this rough path for the first time and charts it, it does become much easier for others to follow it later on, but it still requires a lot of effort to go through them, because there are still a lot of rough bushes and some parts of the map are not very clear (reading and reproducing the research paper to further advance the state of the art).As enough people start going through, the probability that someone with a bad memory ends up walking it increases, and that person ends up pounding the earth into a beaten track and increasing the trail clearance of the beginning of the trail at least (review paper).There finally comes a point when even the local government starts to notice this trail is important, and pays someone to add some stone pavement and rails on the most exposed parts of the trail (post and undergrad education).And at last, Ciro Santilli comes with a bulldozer and creates an autoroute that thousands of people can cruise at high speed without any effort (Q&A, open knowledge HTML websites).
Ciro's documenation obsession is partly part of his braindumping effort of dumping his brain into text form, which he has been doing through Ciro Santilli's website.
UK shirt size: L.
UNIQLO leggings size: L.
Shoe size 30 year old, as in 2017-04 Nike Flex Experience RN 6 Grey running shoes:
- US: 11
- UK: 10
- EUR: 45
- cm: 29
31 year old:
- Height:
- Weight:
- Chest: 94cm
- Waist: 81.5cm
- Hip: 85.5cm
- Inner leg: 92.0cm
- Inseam: 95.0cm TODO vs inner leg. This was a separate measure from crotch to ground with help of wife.
- Length of back: 71cm (from base of neck to knuckle height)
- Collar: 38cm
- Sitbone distance (ischial tuberosity):
- sitting on cardboard: 110mm, this method felt accurate
- www.youtube.com/watch?v=xSWlwzqGKik water method: 90mm/100mm. Small butt!?
- Arm sleeve length: 61.5 cm
- Head circumference: 58.5 cm
- Hand:
- circumference: 19.8 cm around open hand knuckle
- Tip Of Middle Finger To Crease Under Palm: 20 cm
- Circunference around closed knuckle: 25 cm
- Hand great span en.wikipedia.org/wiki/Span_(unit): 0.22m
- Erect penis length: just kidding, just kidding. Ciro Santilli's wife would kill him.
- rest heart rate: 60 BPM
Sight:
- 32 yo:
- R SPH -1.50, CYL -0.5, AXIS 150
- R SPH -1.25, CYL -0.5, AXIS 3
Underwear:
- L from Mark & Spener in UK was humongous. Lets felt tight at first fitting, but it quickly expands to normal size after wearing once.
Ciro Santilli's dreams almost all include the following aspect: Ciro is trying to do something mundane, like climbing a hill, walking across town, etc. but doing so it extremely difficult. The hill is too steep, he gets lost, and things which are easy to use in real life are impossibly hard to use in the dream.
So they are a bit like nightmares, but not that bad. Just really annoying and tiresome. Still, Ciro does enjoy o visiting the semi-real places those dreams bring him to, much for the same reasons he enjoys cycling.
Ciro attributes this type of dream to his occupation as a software engineer, because that's basically the feeling you get all day from it: why isn't this working!!! It is so basic!!!
As mentioned at Section "Linux Kernel Module Cheat", this should be merged into that other project.
There are unlisted articles, also show them or only show them.