When you aren’t feeling that async energy but you still get a callback.

{
  "false": "ok"
}

Uhh, I mean this pragmatic workaround

Not much, what about you who?

Sharded RDBS gets you very very far from my experience at least.

I didn’t expect the FP inquisition.

Priest: If you are not yet baptised, I baptise you in the name of the father, the son and the holy spirit. Else break.

Parents: *sweating nervously*…else what

Seems pretty luck of the draw at least in my area. I’ve had some absolutely fantastic technicians and some who seemed to just want to hand wave away my issue.

Plus most drop downs allow you to type anyway from memory.

Pack a bag, we need to be far away from here in the next 3 to 4 business days… don’t ask why just pack!

I remember this too… what a nightmare.

Ohhhh right, that’s the base part right?

Just if you need to be able to take it with you.

Do you have to print it out and scan it first?

Hey that’s no fair, it’s still test driven development but the test just runs in production!

Exactly, the climates always changing. Just look at the graph, all the bars are different heights so there’s no reason to believe anything different is going on now.

EDIT: damn, things must be really bad if I need the /s here.

The secret to all issues in code and in life.

I wouldn’t deploy this for my fucking dog, roll it back now!

I enjoyed the joke but yeah I thought Rust was known for quite good error messages in general. I haven’t used it though myself.

I personally drive my car like a maniac therefore this study must be false… really?