Said family member mentioned in the parent thread keeps a handheld radio (I don't know the exact tech specs, sorry) for such occasions. That said, they mostly use it to just listen for any logging trucks calling out checkpoints so they can avoid getting in their way when travelling to their remote campsites.

Coupled with a Garmin inReach w/ backcountry maps installed, it gives us peace of mind in case something goes wrong out in the bush.

For anybody with friends/family in the area, the BC subreddit megathread[2] on this is a good starting place to get information on evacuations, power outage status, road closures, official relevant Twitter accounts, etc.

1: https://goo.gl/maps/CXcNEUmAx8gpF5CTA

2: https://www.reddit.com/r/britishcolumbia/comments/qubkc6/flo...

For the government/secret partition, I have no clue what their SLA is, but it wouldn't be a leap to assume they may something different.

1: https://www.amazonaws.cn/en/management-console/faqs/

2: https://aws.amazon.com/premiumsupport/knowledge-center/brows...

My favorites for retro-like discussions (if you think it will be beneficial):

1. What did you worry about the most in the beginning that later turned out to be silly/inconsequential?

2. What did you intentionally put off in the beginning thinking it wasn't a big deal that you later regretted not spending more time on?

That said, it's nothing super fancy. Simple collaborative sticky note app that supports Markdown and has the ability to vote once per sticky.

After the 20ish or minutes of silent reading, we give people ~5min to post their questions for all others to see in real-time. We then give people a set number of votes and the presenter goes through the list answering the questions in descending order of votes.

I was hesitant at first when they introduced this (since it felt like more red tape), but I've found it helps focus the discussion on the most important feedback while avoiding one person bikeshedding the discussion time right at the beginning.

Your story motivated me even more to keep nurturing my niece's interest in programming :)

I've worked with UX/UI designers across multiple companies for over a decade, and the simpler something seems (i.e. making a new logo) the more time & resources it usually takes to do properly.

If this truly comes to pass, then I couldn't imagine the difficulty of having to re-brand AWS in China that'll make both the CCP and AWS' leadership happy.

Comments URL: https://news.ycombinator.com/item?id=25283725

Points: 2

# Comments: 0

I soon realized, however, head-in-the-sanding the other current use cases and their complexities would be an amateur mistake.

Bank accounts (ACH/SEPA), EU's relatively recent push for MFA for credit card transactions, India's mandate overall for MFA, China's gov't regulations around customer payment data not leaving the GCF, validation of China Union Pay cards in North America, etc., are all complex instruments/workflows that are no small feat to handle and handle well.

Easily took away 75% of the stress at work and stopped from it bleeding into my private life.

This can manifest itself as: - being upfront with what you do and don't know when asked to do anything so if delays occur, it won't be b/c you overpromised == lose trust - keeping stakeholders in the loop with any significant developments so there are no surprises down the road - estimate normal project work as if you can only work ~8 hours a day/5 days a week (while taking meetings, vacactions, other normal overheads into consideration)

This, IMHO, is a pre-req to properly implementing any of the other common helpful tips others have listed.

Yup - I think that lines up.

> what is the master aggregate "switch" ? what does it do?

We have a hierarchy of aggregrate monitors (or "switches") that watch n amount of either specific metrics or other sub-aggregate monitors.

In the case of production deployments, we watch a specific rollback aggregrate monitor for either a fixed amount of time or customer traffic that will auto-trigger a rollback if it goes into alarm (aka switches on).

We also have a master aggregrate monitor that will switch on if any sub-monitors get swtiched on for any reason. We typically watch this master aggregate alarm to auto-disable any promotions in our code pipeline.

For me, currently, "canary" means a set of basic automated integration tests that are continually running in production with alarms that feed into a master aggregate "switch". Wether the dedicated canary accounts end up hitting a one-box prod host or real prod host in the end isn't a factor.

The important thing is we incrementally expose our latest code commit to prod hosts via one-boxing to reduce the customer exposure if an acute problem somehow gets past the previous code deploy stages/tests.

One downside - depending on your setup - is you may not have an easy way to hit the hosts directly/deterministically via any UIs in case you wanted to do any manual verification/debugging yourself.