Code now, promises next, timers later

JavaScript finishes the synchronous code it is running before it looks at any queue. Then it drains the microtask queue, where promise callbacks wait, and only afterwards runs the next timer or event callback. A setTimeout of 0 ms still goes to the back of the line behind promise callbacks.

Read it once, then a question tests whether the trick stuck.