Ciro Santilli @cirosantilli 40

Utah's mormon-uni.

Simulates vintage hardware synthesizers, and includes some pretty complex ones!

Aims to show an UI that looks exactly like the synthesizers in question.

For example for the Minimoog on Ubuntu 20.04:

This is a really good piece of software. You can search on YouTube how some classic synths, work, and the immediately start playing them!

One of the defining properties of algebraic structure with two operations such as ring and field:This property shows how the two operations interact.

See: math.stackexchange.com/questions/579453/real-world-application-of-fourier-series/3729366#3729366

Subcase of antisymmetric multilinear map:

They are sorted in order of "most likely to get done first".

Top one: OurBigBook.com.

A 4D gradient with some small special relativity specifics added in (the light of speed and sign change for the time).

Some notable examples:

Example: sqlite/ip.c, adapted from www.sqlite.org/loadext.html, also mentioned explained at: stackoverflow.com/questions/7638238/sqlite-ip-address-storage/76520885#76520885.

Sample usage in the test program: sqlite/test.sh.

Docs: www.sqlite.org/loadext.html

Example where this level is sufficient: nodejs/sequelize/raw/parallel_update_async.js.

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.

If session autosave was finally mainlined, this would be Nirvana.