crehn

Totally arbitrary. In French 2ème Janvier 1900 would be the most common.

> #1 Happiest country in the world

As a Finn, this is always funny to hear. I have no idea where they draw their conclusions from. :^)

BBC still has a frustrating bug on mobile:

  1. Tap on Most Read
  2. Tap on any story
  3. Tap back in the browser

It'll go back to the Most Read tab, then after a second switch to the Latest Stories tab.

The "oh yeah" has a sexual intonation to it; it's perfect.

Off-topic, but wanted to call out the pleasing design. Loving the miniminal/visible/crisp/high-contrast shapes and legible fonts.

Chime does too. And it feels very clumsy.

Technology has advanced so much, yet the UX of real-time video interactions is dreadful. No exceptions.

I'm expecting a lot of potential improvements and opportunities in this area.

Also propofol is fun. :^)

My attempt at explaining why periods at the end feel uncomfortably stiff in a Slack-like environment:

Social conversations are fluid and open-ended, with participants organically shifting between listening and speaking. A period however conveys finality, which is off-putting in such a human setting.

For example, “No.” sounds like the very stern “No” of someone who’s not willing to listen or discuss any further.

This is some next-level rap music, nice.

Is it similar to how changing FOV in a game makes the movement appear slower/faster, but in both cases the space traversed is identical?

This reminds me of when you could order free Ubuntu CDs.

Can you name a few of the billion places? Of course with similar potential impact as Twitter, and without the censorship.

UX overall is under-appreciated. It's very hard to measure "soft" attributes (effects of aesthetics, chaos/consistency, ambient stressors, physical exertion, etc. on mood) of humans, hence harder to gain consensus. It's unfortunate it has such a tremendous impact on humanity, yet we have such bad instruments to measure it.

I never use any protection on my iPhones. I find cases ugly and bulky; I want to enjoy the device's feel, design and engineering.

The iPhone 8 with it's full-glass enclosing has been surprisingly sturdy, surviving even rough drops with only a scratch. Plus if it breaks, I get two replacements with AppleCare, and the process is ridiculously smooth.

I’m assuming this is a joke, but this is exactly what most people who just want to run some code don’t want to deal with.

It’s acute.

Nobody’s saying serverless makes monitoring unnecessary. But a serverless architecture gets rid of an entire category of bureaucracy and issues that can arise from dedicated servers.

The psychological effects of technology seem often overlooked—and they’re hard to quantify.

I wish there was some easier way to quantify the “soft” aspects of everything that surrounds us, e.g. the long-term impact of beautiful and usable UI design, the reduction in “ambient” psychological stress, the impacts of chaos/consistency on how we feel, any robust measures of happiness, excitement, relaxation, etc.

They seem to be such important attributes, but not as easily measured as a latency. Which in turn makes reaching consensus harder—and probably why design by committee doesn't work?

And I’d argue the mere possibility of the server breaking at any time contributes to non-negligible amounts of sustained psychological stress.

Is there a specific reason early settlers would decide to stay in such harsh climates? Risk/benefit of trying to wander somewhere else?

Surely they would be aware of the benefits of warmth, and perhaps know there are warmer places on Earth?

How do we ensure Twitter’s censorship is and stays reasonable?

How frequent are outages and operational issues with DNA?

From a purely UX perspective, there’s a huge difference between “no lines of code” and “a few lines of code”.

Totally agree. I sense ML in general can benefit tremendously from buttery-smooth UX, something it has typically lagged behind on.

Keep it up Nidhal, you’re doing a tremendous service. Don’t let the snobs get to you.

Apple's obsession over small details and creating a delightful UX.

Happy someone else echoes my sentiment too, especially when Ruby seems to be beloved by everyone around. So many ways of doing the same thing; unnecessary cognitive burden for both reading and writing.

For better or worse, I feel that one "simple" change that would make any project more attractive to newcomers is switching to GitHub for development.

So you're just going to mention the recording without sharing it?

A much saner heuristic could use a reasonable range (for some value of reasonable) around the current timestamp to check whether it's also one. The assumption being that logs will be streamed, hence any timestamp will likely refer to something that happened in the recent past.