sre_ops

Yes. It currently runs over 70% of global internet and considering all kinds of error conditions that show up on the global internet the code is extremely stable.

They do the most important thing - they leave.

It will be swallowed by an immediate increase of the price of goods and services UBI would be spent on.

Swiss mostly regulate ammo, not guns.

Postmark is super unreliable for large volume - their servers are down periodically and their email is periodically delayed for hours.

It still does not support multiple admin roles per account.

In that case why do these people care that they dont get hired?

> Then the technical interview came, and one of the interviewers was instantly hostile as soon as he saw me. It was weird. Weird to the point where the other tech interviewer started playing good cop, saying things like "he just covered that" and "no, that's true". Whiteboard coding is strange enough, but doing it with zero feedback and a hostile interviewer who keeps trying to push you in bad directions (inheritance over composition, singletons, etc.) is, well, interesting. The application came back with the inevitable "good skills but bad culture fit" euphemism.

Wait, you think the companies that have to move fast have the coddling environment?

> magine that each Python module runs as a microservice. For many modules this would lead to huge performance degradation, for example a regexp module can be called thousands times per second, the running time of a call is usually short and replacing an in-process call with a network call will give 100-1000x slowdown.

This is absolutely irrelevant. If your call budget is 400ms then extra 4ms that it takes fetching a data from a micro service is negligible. Make 400ms 4ms and you are done.

Example of micro services that just work (tm): Internet.

That's because you are looking at the wrong problem.

The biggest problem with common core is that it codifies social promotion under the guise of "schools know better" while linking promotion to money received by the schools.

Tax payers aren't funding publishers. Don't like it? Go publish it on your blog.

Yes, publishers should work for free. plonk

Oh this is going to be fantastic. I cannot wait until the public see what kind of junk is produced by these "researchers" in their original form.

Well, if you want to never write anything that scales yes, those are in fact the correct practices for writing bone-headed APIs for applications that would blow up with 20k concurrent users doing simple GETs.

If for some unknown reason you want to write APIs that don't go down faster than a 15 year old girl faints upon stumbling onto a boy from 1D in a local McDonalds you should:

a) use verbs

b) separate heavy end point from light end points

c) make URL easy to parse by load balancers and proxies