fxn

On a Virgin cruise near Ibiza, getting ready for it before sunset. Anyone else in the cruise say hello!

That is not the hallmark of literate programming, but the hallmark bad/unhelpful code comments or docs. Like, you can also have bad/unhelpful function names or unclean and tangled implementations.

"TeX: The Program" is a joy to read.

The remontoire has a technical/practical modern use in the Zeitwerk.

No.

This is not true.

In Ruby, tests are the same you'd write in any other language. You test that things do what they are supposed to do, not the types of parameters or return values.

The Atmos does not have a seconds hand. All models except two do not have minute indications.

I believe that is going to difficult measuring accuracy. You can approximate something if you compare it over a long period of time, perhaps at 12 o'clock, or as much 12 o'clock as you can tell by inspecting the hands alignment.

It is read-your-writes semantics, and the metadata is stored in the session.

It is your choice. You are in charge and freelancing gives you the opportunity to bill _less_ and leave space to other important things in your life for which a regular job would compete. Family time, sports, hobbies, learning new things, etc.

This project is wonderful. Dozens of cities over the world are opening their doors to its citizens thanks to it. In Madrid, inhabitants have a direct vote on how to spend _millions_ of the city budget.

I wish the future of our society goes in this direction.

I have tried a bunch. Notion is super cool, but doesn't do tables at this moment (though they seem to be working on it). Some apps have one level of nesting only, which is not enough structure for my use case. By now I have settled on Dropbox Paper.

Also, having a WYSIWYG editor is cool, in raw Markdown links and images just do not look good for my taste (and tables, and more, compared to Dropbox Paper or Notion). The number of files for which they support syntax highlighting is small though. In particular Elixir is not in the list as of this writing.

IMO an ORM is not a substitute for knowing SQL, much less studying the actual database.

To me, an ORM is a tool that allows someone that knows SQL to write statements they would write by hand using business-level vocabulary.

Also, you have to be savvy enough to know when you are hitting the max expressiveness of the ORM and need some powerful SQL you better write by hand. Active Record certainly provides API for that, and it is an API you are supposed to leverage when the circumstance arises (Rails team over here).