FrancoisBosun

Meh, I tell it "use uuidgen and get your randomness from that". Of course, that won't work on ChatGPT web, but works well enough on the command line.

Explained in the article:

> A producer sends a backing track to a performer - SyncDNA adds a slight delay to the outbound feed

The "backing track" is probably the beat or something similar.

I do the "same thing", but using PostgreSQL `EXPLAIN ANALYZE`. EXPLAIN ANALYZE has information about the number of rows returned, which means I know exactly which node in the query plan failed to return expected values.

This has some overlap with Overmind / foreman / Procfile. To wait for another process to be started, I resort to using plain `sleep` or `dockerize -wait`.

Good job on building this!

In the article, it is mentioned that « we can grant temporary access to cardiac-related data » (paraphrased). This is where it gets difficult: how am I to know that some data is cardiac-related or not? Is it important to share my thyroid levels or not? This is a very difficult problem. I wouldn’t know what to share for medical history.

Sorbet is nice, but for data structure enforcement and data validation, I much prefer the dry-rb ecosystem.

Heroku's 25 hours comes to mind... this is so infuriating and annoying.

You still need the timezone name to map back to UTC, in case you want to make some types of computations, usually along the lines of "how long ago was this" and "remaining time until this thing happens".

You may argue that we can use local time to make the computations and be done with it, but during DST transitions, local time jumps so the number of actual seconds won't be consistent.

I use an older iPad and the page crashed so hard the Home button didn’t do anything for about 30 seconds. The iPad eventually turned off, because I had pressed the power button, to no avail, a couple of times.

C, C++, C#, and probably Rust. There’s a section about that. There’s a link to the FAQ I. That section.

Not so different from Word/Excel/Lotus 1-2-3 from the 90s! I like that most software saves-as-I-type now, but that was the workflow back then. Ctrl+S was the most used key combo on my keyboard back then. Now, it's `:w<Enter>`.