Oncall.

For what types of systems? This is something I've worked on a little bit. How far would you want to outsourcee to go in fixing issues? (Ie how much would you trust them to touch/change?)

Totally agree, sleep is most important. I was in a phase a few months ago, where, I felt like a zombie. I fixed that, by eliminating coffee or any other source of caffeine. I can now sleep within seconds as I lay down on my bed. I generally tend to feel fresh after a night's sleep. And, it's crazy how deeply I can focus during the day now.

That's why I login into my bank or other important accounts in incongnito mode, where, I make sure extensions stay disabled.

+1

If the article had used I/O (http request) as an example of event handling (message queuing), it would have added some concurrency context.

setTimeout uses the same message queuing system as XHR, DOM events, or communicating with stuff that has its own stack like iframes or workers. That's why a function with a timeout of 0 will not fire until after it's enclosing function has popped. Functions block. Waiting for messages doesn't. That's the model for JS concurrency.

I agree.