Toy model of matter that exhibits phase transition in dimension 2 and greater. It does not provide numerically exact results by itself, but can serve as a tool to theorize existing and new phase transitions.

Each point in the lattice has two possible states: TODO insert image.

As mentioned at: stanford.edu/~jeffjar/statmech/intro4.html some systems which can be seen as modelled by it include:

Also has some funky relations to renormalization TODO.

Bibliography:

A slow development test cycle will kill your software.

New developers won't want to learn your project, because they would rather shoot themselves.

This means that build time, and the time to run tests, must be short.

5 seconds to rebuild is the maximum upper limit.

Of course, at some point software gets large enough that things won't fit anymore in 5 seconds. But then you must have either some kind of build caching, or options to do partial builds/tests that will bring things down to that 5 second mark.

You also have to spend some time profiling execution and build from scratch times.

A slow build from scratch will mean that your continuous integration costs a lot, money that could be invested in a new developer!

It also means that people won't bother to reproduce bugs on given commits, or bisect stuff.

One anecdote comes to mind. Ciro Santilli was trying to debug something, and more experience colleague came over.

To reproduce a problem, ciro was running one command, wait 5 seconds, run a second command, wait 5 seconds, run a third command:

The first thing the colleague said: join those three commands into one:And so, Ciro was enlightened.

The risk–benefit ratio is a comparative assessment used to evaluate the potential risks and benefits associated with a particular action, decision, treatment, or intervention. This ratio helps individuals, organizations, and policymakers determine if the expected benefits outweigh the risks involved, and whether it is justifiable to proceed with a particular course of action. ### Key Components: 1. **Risk**: Refers to the potential negative outcomes or hazards associated with an action.

Ciro Santilli believes that there is a positive correlation between being a software engineer and liking Buddhist-like things.

Maybe it is linked to minimalism and DRY, which software engineers value so greatly.

Even Ciro had to try an unoriginal Buddhist joke intro in one of this Stack Overflow answers.

Ciro also feels that his "minimal reproducible example" scientific language/concept learning method obsession of breaking things into tiny sub-problems has a strong link with Koans.

Some notable Buddhism/programmer examples:

Another thing that points the correlation out is the existence of wattsalan.github.io/ on a github.io about Alan Watts.

Hmmm, he does not know how to spell guerilla? sic? www.quora.com/What-is-the-correct-spelling-guerilla-or-guerrilla

Note to self: if you are going to commit a crime, don't publish your plans online.

Ross Ulbricht's diaries come to mind.

That's how Russian shadow library maintainers do it, they know how to crime good old Russians. Maybe there is a good thing about having dictatorships in the world that give zero fucks about American copyright laws. There will always be some random Russian academic who will implement this and not go to jail. Maybe it's even state sponsored.

As of my last knowledge update in October 2021, Rien Kaashoek does not appear to be a widely recognized figure or term in popular culture, history, science, or significant events. It's possible that it could refer to a private individual, a lesser-known public figure, or a term or concept that has gained relevance after that date.

Zephyr is cool. Its installation setup is annoying. But the project is cool.