Amazing talk by Richard Feynman that describes his experiences at Los Alamos National Laboratory while developing the first nuclear weapons.
Video 1.
Los Alamos From Below by Richard Feynman (1975)
Source.
Polynomial over a field Updated 2025-07-16
By default, we think of polynomials over the real numbers or complex numbers.
However, a polynomial can be defined over any other field just as well, the most notable example being that of a polynomial over a finite field.
For example, given the finite field of order 9, and with elements , we can denote polynomials over that ring as
where is the variable name.
For example, one such polynomial could be:
and another one:
Note how all the coefficients are members of the finite field we chose.
Given this, we could evaluate the polynomial for any element of the field, e.g.:
and so on.
We can also add polynomials as usual over the field:
and multiplication works analogously.
Polynomial over a ring Updated 2025-07-16
However, there is nothing in the immediate definition that prevents us from having a ring instead, i.e. a field but without the commutative property and inverse elements.
The only thing is that then we would need to differentiate between different orderings of the terms of multivariate polynomial, e.g. the following would all be potentially different terms:
while for a field they would all go into a single term:
so when considering a polynomial over a ring we end up with a lot more more possible terms.
The inaugural that predicted the Josephson effect.
Published on Physics Letters, then a new journal, before they split into Physics Letters A and Physics Letters B. True Genius: The Life and Science of John Bardeen mentions that this choice was made rather than the more prestigious Physical Review Letters because they were not yet so confident about the results.
Git design rationale Updated 2025-07-16
The fundamental insight of Git design is: a SHA represents not only current state, but also the full history due to the Merkle tree implementation, see notably:
This makes it so that you will always notice if you are overwriting history on the remote, even if you are developing from two separate local computers (or more commonly, two people in two different local computers) and therefore will never lose any work accidentally.
It is very hard to achieve that without the Merkle tree.
Consider for example the most naive approach possible of marking versions with consecutive numbers:
  • Local 1:
  • Local 2:
    • 0: root commit
    • 1: commit 1
    • 2: commit 2 by local 2
    • 3: commit 3 by local 2
  • Remote
If Local 1 were to push to Remote first, how could Local 2 notice that when it tries to push itself? The navie method of just checking: "does Remote have commit "2"" does not work, because Local 2 has a different version of commit 2 than local 1.
By GitHub around Black Lives Matter, due to a possible ludicrous relationship with slavery of black people:For the love of God, the word "master" is much more general than black slavery. If you are going to ban it, you might as well ban the word "evil".
Several software projects followed the purge from their codebases, maybe GitHub followed someone else's lead, it's hard to say.
The words "whitelist" and "blacklist" were also targeted.
GitLab Updated 2025-07-16
GitLab was very important to Ciro because he wanted to base Booktree on it.
These are good free newbie GUI options:
sudo apt install meld
git mergetool --tool meld

sudo apt install kdiff3
git mergetool --tool kdiff3
https://raw.githubusercontent.com/cirosantilli/media/master/meld.png
https://raw.githubusercontent.com/cirosantilli/media/master/kdiff3.png
Let's make a more interesting conflict:
git-tips-2.sh
#!/usr/bin/env bash

set -eux

add() (
  rm -f f
  for i in `seq 10`; do
    printf "before $i\n\n" >> f
  done
  printf "conflict 1 $1\n\n" >> f
  for i in `seq 10`; do
    printf "middle $i\n\n" >> f
  done
  printf "conflict 2 $2\n\n" >> f
  for i in `seq 10`; do
    printf "after $i\n\n" >> f
  done
  git add f
)

rm -rf git-tips-2
mkdir git-tips-2
cd git-tips-2
git init

for i in 1 2 3; do
  add $i $i
  git commit -m $i
done

add 3 4
git commit -m 4

add 5 4
git commit -m 5

git checkout HEAD~2
git checkout -b my-feature

add 3 6
git commit -m 6

add 7 6
git commit -m 7
Good targets for amateur astronomy Updated 2025-07-16
Looking at most astronomical object through a telescope is boring because you only see a white ball or point every time. Such targets would likely only be interesting with spectroscopy analysis.
There are however some objects that you can see the structure of even with an amateur telescope, and that makes them very exciting.
Some good ones:
Good video game to watch Updated 2025-07-16
This is a list of video games that are good to watch other people playing, even if you don't play yourself. And often they are better to watch than to play as you don't have to waste your time as much!
Google X Updated 2025-07-16
Wikipedia reads:
Any contributor could create and own new Knol articles, and there could be multiple articles on the same topic with each written by a different author.
so basically exactly what Ciro Santilli wants to do on OurBigBook.com. Ominous.
Like any closed source "failure", everything was deleted. wiki.archiveteam.org/index.php/Knol
History of special relativity Updated 2025-07-16
Bibliography:
Video codec Updated 2025-11-18
History of Wikipedia Updated 2025-07-16
A 2022 clone of phabricator.wikimedia.org/source/mediawiki.git gives first commits from 2003 by:
TODO when was wikipedia open sourced from Nupedia? The early days of Wikipedia are quite obscure due to its transition from Nupedia.
Hofstadter's law Updated 2025-07-16
The trivial takes a few hours.
The easy takes a week.
And what seemed hard takes a few hours.
As "deadlines" approach, feature sets get cut down, then there are delays, and finally a feasible feature set is delivered some time after the deadline.
The only deadlines that can be met are those of tasks which have already been done but not announced.
This is of course Hofstadter's law.
On the other hand, as a colleague of Ciro once mentioned, it is also known that the time it takes for a task to be done expands without limits to match the deadline. And therefore, without deadlines, tasks will take forever and never get done.
And so, in a moment, perceiving this paradox, Ciro was enlightened.
I can't believe there isn't a YouTube video comparing various substances for each flammability and instability ratings, this would be a huge hit.
There are apparently two methods:
Specific implementations:
How to teach and learn physics Updated 2025-07-16
The approach many courses take to physics, specially "modern Physics" is really bad, this is how it should be taught:
This is likely because at some point, experiments get more and more complicated, and so people are tempted to say "this is the truth" instead of "this is why we think this is the truth", which is much harder.
But we can't be lazy, there is no replacement to the why.
Related:

Unlisted articles are being shown, click here to show only listed articles.