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`.
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.
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.
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>`.
This looks very, very interesting! Good work. My only nitpick is the ligatures. I believe pipelining in Elixir uses the |> operator, but the blog post uses a kind of triangle pointing to the right. Due to my previous exposure to Elixir, I guessed that it must have been |>, but if I hadn’t know, then I would be really confused when I tried to write that in my editor to replicate the code.
I'm mostly surprised about the free admission of bribery:
> However, I soon found that a bottle of Johnie Walker Black Label handed out at particularly frustrating moments made things miraculously happen a lot quicker. Oh how the North Koreans loved their whiskey.
I use an iPhone 12 mini. In portrait mode, the site was nearly unusable. I would add a habit, and the keyboard covered up the description field. There was no way for me to scroll the page to get the description field. Fortunately, the iOS keyboard has a next field button which I could click and hello me to entered the habit description.
I too like the clean design and wish you good luck.
They don’t. They’re using another phone and texting the original owner, threatening them, in order to scare them into unlocking the device.
When you boot the “Lost” phone, it asks for the password of the owner’s iCloud account. There is probably an information leak where the original email or phone is presented and the thief can track the original owner through that.
Adding an index means the write path suddenly became slower. Sometimes, a covering index will be very beneficial. « It depends » is usually the right answer. I’m fine with the engine telling me « this query is usually slow » and I investigate why. I’m not ok with the engine adding indices willy-nilly and suddenly writing to the DB is 10x slower.
I enjoyed my game. I had some difficulty playing due to the board not being very wide: many nooks and crannies. In the dictionary, search for « ti » and notice the invalid character in « solfage ». Congrats!
SQLite, as used in the article, has a very simple data model: 64 bit ints, 64 bit floats, and textual data. If you used a different database engine, you would probably use the datatypes it offers instead.
Not the author, but PostgreSQL has constraint triggers that can run procedures / functions on insert/update/delete, to allow/reject a given row or statement. That would be one way to confirm that a given update from a client is valid, from the POV of the application.
It is striking that most generated photos have the woman on the left. Only two states have the woman on the right. This is probably due to the source material the AI was trained with, I understand, but that was striking anyway.
Human taste would have chosen to vary the poses as well, because the pictures kind of all have the same look.
« … With Ruby Infrastructure. » Ruby isn’t doing the compute. Instead, Ruby is used to distribute and run workloads on individual machines. The underlying project is Peplum: https://rubygems.org/gems/peplum/versions/0.3.3
The downcasing in done in Ruby-land, thus the records had to be loaded in memory, on the worker. If the downcasing was done on the DB itself, then the records would not have needed to travel all the way to the worker, only to be discarded 200ms later. Better to run an UPDATE query direct against the DB instance, with IDs to control concurrency: UPDATE addresses SET city = lower(city), state = lower(state) WHERE id BETWEEN a AND b
When the dependency is deprecated, I have to stop what I'm doing and replace the dependency. If the dependency has a show-stopper bug, I either have to wait, vendor the dependency, or rewrite. That's what the original article advocates for: be careful what you import. leftpad, probably write it yourself. React, OK to use, but maybe vendor.