trentdk

Seemed like a fine comment. I now know there are people who think those mentioned technologies are important enough to require mention in this sort of write-up. I’m now curious, and will look them up.

On the flip side to your closing statement, YouTube has been a boon to DIY. What used to be trade secrets are now on display by people all all professions. Anecdotally, I’ve remodeled nearly my entire house over they past ten years with YouTube.

Insightful, thanks.

My mind just exploded. Would you have to breach a threshold to jump to the next state?

I think what we’re concluding here is that using Google to obscure the linguistic style is flawed, because a state actor could obtain the original linguistic style from Google records, or from their own records of snooped traffic.

In other words: the blog should find a way to obscure linguistic style offline.

The idea is to stop the respiratory droplets that contain viruses. Droplets measure on the order of micrometers, which is the range that surgical masks are made to be effective.

A Google search result for droplet sizes: https://www.pnas.org/content/115/10/E2386

A Google search result for effectiveness of various masks related to particle size: https://blogs.cdc.gov/niosh-science-blog/2009/10/14/n95/

I wish this was the top comment; it would save us a lot of debate :).

A major benefit to microservices (over monoliths) that I haven’t seen mentioned yet is testability. I find it hard, or improbable to achieve a healthy Pyramid of Tests on a large monolith.

For example: a high level, black box test of a service endpoint requires mocking external dependencies like other services, queues, and data stores. With a large monolith, a single process might touch a staggering number of the aforementioned dependencies, whereas something constrained to be smaller in scope (a microservice) will have a manageable number.

I enjoy writing integration and API tests of a microservice. The ones that we manage have amazing coverage, and any refactor on the inside can be made with confidence.

Our monoliths tend to only support unit tests. Automated end-to-end tests exist, but due to the number of dependencies these things rely on, they’re executed in a “live” environment, which makes them hardly deterministic.

Microservices allow for a healthy Pyramid of Tests.

I appreciate your thoughts, but they are sad thoughts to me.

Isn’t there something about “exploration” that seems important to a non-neglible amount of humans? I don’t want everything we do to serve the rat race we’re in. Let’s loose our money on something amazing.

I didn’t feel like it painted just middle management as the good guys; it argued that all levels played some sort of managerial part.

Also, I think it argued that the costs saved from concentrating management went mostly to shareholders and executives.

This reply seems overly aggressive; am I missing something?

I thought as a joke that the API is so old, that they didn’t treat women passengers with the same formality. Well... that might be true. In the documentation linked, I see no example of “MS” or “MISS”.

http://www.amadeus.com/bg/documents/aco/bg/basic-qrg.pdf

Page 33