I tried to elaborate that they're not purely random (and we can probably predict a patient's visit time based on history and description of the case), and we can already do some optimizations based on average visit times. Unfortunately his opinion didn't change.

His response was "it can't be done", his argument being that patient visit times are random.

I always spend at least an hour waiting for my appointment at the doctor in Jordan. Today after a 2-hour wait, I offered the doctor to optimize waiting times without any loss of business, for free.

I ended up trying @Shortwave, I was very excited, but it sucked too. Every time I ask anything it only checks a max of 100 email threads before it answers. Needless to say "organize my inbox" (a prompt they promote) is useless if I have ~1500 unread email and they read 100 only.

Come on, #AI integrated into #Gmail should be able to do better! Reminds me of when Google Home understood "Turn off the lights in the kitchen" but not "Turn off the lights in the kitchen and bedroom". When will assistants actually act as assitants?

What does this #Ruby code print (12, or 124), and how do you explain the behavior of break in #Ruby?

How excited I was about #BTC at $7, it's hard to believe today.

Introducing complexity should be strongly justified. "I might need this extra abstraction in the future" is not strong enough. If you really believe you will need it, write code that can easily be refactored, but don't introduce the abstraction until it is necessary.

@fmardini Apart from helping me get unstuck, his book had a motto very relevant to what I'm doing: "The purpose of scientific computing is insights, not numbers". (6/6)

I got stuck in tracking my roundoff errors. I chatted with @fmardini about it. He pointed me to a book by Richard Hamming (whom I admire). (5/6)

Although I had read a bunch before jumping into writing code, nothing teaches you as well as doing the work itself. Getting stuck then unstuck is the exact place where you learn the most. (4/6)

I decided to go ahead with the project nonetheless; my goal isn't efficiency but rather to learn. (3/6)

The most efficient algorithm can't be run in a distributed fashion efficiently (which is why all records held for calculated digits of Pi in the last 10 years were run on a single machine). (2/6)

A couple of weeks ago, I wanted to pick up a new side project and decided to work on a distributed calculation of #Pi. (1/6)

I've been looking for an apartment with a view. My geeky solution: pull 30m resolution altitude data of the city, calculate the gradient at every point, overlay a map, and find the most likely places to have nice views.

Real cool and out-of-the-norm terminal tools and libraries:

Today I learned that you can use 𝚌𝚑𝚊𝚝𝚝𝚛 +𝚒 to make a file immutable, making its metadata (including ownership, and ACLs) unchangeable even by root until the attr is removed. It took me 30 minutes of trying to delete a file to figure this out.

There is an AI for everything:

Exploring CSVs in the terminal? csvlens [1] to the rescue! [1]

One potential downside is that a new family name will just last for two generations, but these days long lineage matters less, and maybe not maintaining it can be an upside (when you considure tribalism). 5/5