It’s a sane scripting language. It encouraged me to automate simple tasks, create handy functions etc. I don’t have to google the for loop syntax every time I need it.
Yes, switching networks can indeed cause users to receive different versions within the 3 hour window. In general we ship small, incremental changes that rarely even are visible to the user, so a small likelihood of serving inconsistent version is acceptable.
Interesting idea with geo restrictions. Does this allow more granularity than country-level filtering? Most of our audience is based in the US, so country-level setting does not give us enough flexibility.
There is also value in knowing the percentage of users receiving the new version. It’s just more predictable and easier to analyze the data if the ratio of new-to-old is known beforehand.
Good question. We just tested with ab (ApacheBench) and consistently observed the difference between Lambda enabled and disabled. We wanted to be sure this system does not incur any significant overhead and that’s why we made sure to only run the Lambda when it is needed.
We hope to see Amazon improving this, as there can be use cases for Lambda@Edge where you can’t restrict URLs so easily.
The story of this checklist has been covered in “The Checklist Manifesto” by Atul Gawande. It’s a great read on how diligence in work can literally save lives. We can advance medicine by breakthrough discoveries that push our knowledge further, but improving how we apply the existing knowledge is just as (or even more) important.
Gawande's essay (and book) on the subject came up just recently in discussion on Hacker News. What it all boils down to is that the medical profession in hierarchical and conservative: doctors don't want to change and don't want anybody telling them what to do.
So was the piloting profession (in part because many pilots were ex-military), and yet somehow, that culture was changed to one of standard procedures, checklists, and Crew Resource Management. I'm still hopeful that the same can happen in medicine.
The relationship between the military and piloting actually may explain why standard procedures, checklists, and Crew Resource Management were more natural than in medicine, despite both being hierarchical and conservative.
I mean, the military is itself a hierarchical and conservative organization in which standard procedures, checklists, etc. are not exactly out-of-norm.
Fair statement but the military also has medical professionals. A wild speculative guess from my perspective is that airlines view it as an objective profession, you do these things to handle the machine and that is end of the story. Medical fields are somewhat subjective since we don't really understand the human body like we do airplanes - we didn't build humans from the ground up. We need to make the medical industry absolutely objective and quantitative in order for procedures and checklists to be effective. It still weirds me out how you need second "opinions" on a diagnosis, it just highlights our inability to understand ailments.
> Fair statement but the military also has medical professionals.
Sure, the military has medical professions, but the military is not as dominant a source of medical professionals as it has been for professional pilots. So, it seems (to me, at least) plausible that military culture might have a substantially stronger impact on the piloting profession than medicine.
My recommendation: configure the shell prompt (add __git_ps1 to $PS1), this saves a ton of time and makes it much easier to understand what is going on. Especially recommended for beginners (but obviously not limited to).
> We could insert new list items into the existing DOM, but finding the right place to insert them is error-prone, and each insert will cause the browser to repaint the page, which is slow.
I don’t think the last part is true. Browsers don’t repaint (nor they reflow) the page until it’s really needed. So if you have a loop that modifies the DOM multiple times, but does not read from the DOM, there performance hit described by the author should not occur.
One can argue if it’s a misuse or not. It’s quite handy to have such utility classes that rely on !important and can be used in markup directly. I have plenty of those in my stylesheets.
Like your article. Especially agree with this phrase "authoring and maintenance considerations should trump kilobyte savings" (within boundaries of course).
