- Understand and check Service Quota of ECS/Fargate and other related services
- Cluster
- CDK for ECS: blog
Sidney Dekker | |
The Field Guide to Human Error - https://amzn.to/2O30hAI | |
Just Culture - https://amzn.to/2XSsIpD | |
RULE- AND ROLE-RETREAT: AN EMPIRICALSTUDY OF PROCEDURES AND RESILIENCE - https://bit.ly/2F9is5e | |
Erik Hollnagel | |
From Safety-I to Safety-II: A White Paper - https://www.skybrary.aero/bookshelf/books/2437.pdf | |
Joint Cognitive Systems: Patterns in Cognitive Systems Engineering - https://amzn.to/2u8jhVE | |
Resilience engineering – Building a Culture of Resilience - https://bit.ly/2J8Calz |
This list has the goal of helping developers interested in contributing to the Go language but are unsure of where to start. This was not generated manually so some functions and methods here may not require examples (maybe because they are too simple, e.g .String()) and some of these may only make sense in a package level example (which are not considered for this list yet). Use your best judgment and check the documentation before you open up a CL to add an example.
You should also search in gerrit for open CLs that are already adding examples.
I will try to keep this list as up to date as possible. If you find any mistakes, please comment below and I will try to fix it.
Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.
This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would
- install gcalcli and connect it up to your account (
gcalcli agenda
after install should start the auth process) - write the python file above to somewhere (I use
~/.i3/cal_wrapper.py
) - setup your
~/.i3/config
with thestatus_command
above - reload i3
I added the following cron entry to alert via notify-send
and dunst gives me warnings
*/5 * * * * gcalcli remind
First you'll want to check if you need a visa to enter the UK.
- Nationals of the EU, Switzerland, and EEA countries will not need a visa, and are free to work and conduct business in the UK.
- Nationals from some designated countries such as USA may travel for tourist or business purposes under a visa exemption. The link above will detail what documents you need to provide in order to travel under a visa exemption.
- Other nationals will need a visa.
The rules for allowable business travel under a visa exemption are covered by the same rules as those travelling under a vistor visa. If you will be travelling under a visa-exemption and the conference is covering your costs in any way you should make sure to read the relevant section below.
# Attribute Provenance reporter | |
# ----------------------------- | |
# | |
# Runs as a ChefSpec test and dumps two sections of data: | |
# 1. all attributes (data from `node.debug_value()`) | |
# 2. where each attribute is set. You can specify the attributes | |
# you want included with an ATTRS environment variable. | |
# | |
# Sample run: | |
# |
Around 2006-2007, it was a bit of a fashion to hook lava lamps up to the build server. Normally, the green lava lamp would be on, but if the build failed, it would turn off and the red lava lamp would turn on.
By coincidence, I've actually met, about that time, (probably) the first person to hook up a lava lamp to a build server. It was Alberto Savoia, who'd founded a testing tools company (that did some very interesting things around generative testing that have basically never been noticed). Alberto had noticed that people did not react with any urgency when the build broke. They'd check in broken code and go off to something else, only reacting to the breakage they'd caused when some other programmer pulled the change and had problems.
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft
,elem.offsetTop
,elem.offsetWidth
,elem.offsetHeight
,elem.offsetParent