alex5207

This is exactly what we're doing. Works like a charm.

[About the event loop]

> She's behind the scenes managing resources. Some power is explicitly granted to her, but a lot of her ability to get things done comes from the respect & cooperation of her subordinates.

What a wonderful paragraph. Playful, yet with a deep meaning. It makes the article a joy to read.

Those are cursed!

> I'm stuck with manual docker compose up/down commands over SSH

Out of curiosity, what is so bad about this for smaller projects?

Super read! Thanks for sharing

Enjoyed the read - thanks for sharing! Found a small typo here:

> For the service rate (λ), we can keep things simple and assume that our server can service 10 items per minute with zero variation.

I think it's supposed to be mu and not lambda

Good point about fluctuating rates for e.g the sales period. But couldn't you then pick a metric that doesn't fluctuate?

Out of curiosity, where did you work? In the same space as you.

Obviously I didn't mean to imply that your merits as a programmer should be judged by your ability to recall specific syntax, like the equality operator in some language.

I'm wondering about the long term effects of not paying attention to such details. Do you miss out on picking up patterns used by a certain library, framework, language or whatever, that you could have used to write your own code better?

Never knew about QUALIFY. That's great

His explanations are great and just wanted to +1 on the idea of range trees. Adding a reference here to a very lightweight read on range trees:

https://courses.csail.mit.edu/6.851/spring10/scribe/lec03.pd...