This week I'm doing an internal talk at Amazon about an approach to system design that I use a lot, and think would use useful to a lot of people: simulation. This thread is a summary of the talk 1/
I've had 3 calls so far today (it's not even 10) about defending against Russian cyber ops
I'm tired of having the same call... so... here's what I've told everyone. This is the playbook you need... but it's not going to be what you think it will be.
Ready? Lets go!
1
Hey, so we organise a conference each year....
blog.dddperth.com/become-a-d…
This year, we are chasing some volunteers, particularly anyone interested in:
1) Logistics, from room layout to choosing what everyone eats!
So I've been working on a thing the past few months and it's now live!
If you want to learn about #a11y and how to test, there's still a few hours left on the sales
Big thanks to @stolinski and the team at @LevelUpTuts for the help and support!
leveluptutorials.com/tutoria…
NEW POST: @evanbottcher explains how strength of alignment varies across an organization, and how that affects decision making
martinfowler.com/articles/st…
"This specification defines a new HTTP method, QUERY, as a safe, idempotent request method that can carry request content."
ietf.org/archive/id/draft-ie…
“And you know that they won’t show their rotten little faces in any aggregates.” 🤣
Anyone who has been wondering what the best way is to explain why you need observability can go home now.. @mipsytipsy won (which will surprise exactly no-one ofc)
You keep an eye out for outliers of any type, until you're satisfied it's baked. Because you *know* that production is the only place interesting bugs show up, and you know that takes time, and you know they won't show their rotten little faces in any aggregates
The goal never is to create an #API. The goal always is to create value for the organization. APIs simply make that easier and faster than it used to be. Focus on the value you actually create, and your API practice will improve as a side-effect.
Serverless is not going to solve your org’s existing skills gap. And for many devs it’s actually going INCREASE the amount of infrastructure and operations complexity they’re responsible for. 1/
While I wait for the GPU to churn through 2*26^11 possibilities, a brief recap of how we got here. It started when I noticed this bit of code in the @GitHubCopilot Visual Studio Code extension that detects naughty words in either the prompt or the suggestions.
ALT Screenshot of the Github Copilot Visual Studio Code extension, showing an obfuscation (hash) function and the start of a large array of hashes.
Strategy isn’t your day to day: it’s the context within which your day to day makes sense.
Strategy isn’t every decision upfront: it’s what gives the daily decisions context and coherence.
This is also true of @Monzo and we're yet to have an outage due to region failure. We've also built many improvements to the platform with the time we would have spent chasing the multi-region hype.
Fun fact: Amazon.com is served from a single region. Don't buy the whole 'you need multi region' thing too early. It is often not a differentiator or requirement and it will slow development down considerably.
“A product manager whose schedule is not affected by low-quality automation will always prioritize new features over simplicity and automation.”
— Google SRE book