Categories
links

Links

  • The Document Culture of Amazon: Team member’s can cancel meetings that don’t have a document. The first 5-10 or more sometimes minutes of every meeting are spent by having everyone in the room reading about the issue under discussion so everyone starts with similar context and can participate. 1-pagers, press releases, FAQs, or 6-pages are the different formats. I’m going to try doing this in my meetings. Let’s see what people think 🙂
Categories
links work

Links

Categories
links

Links

Categories
links

Links

  • HL7 Fhir: A standard for health care information exchange between disparate software systems. Restful. Well specified. The problem we’re trying to solve is to allow controlled, specific movement of health data between systems to open up possibilities for collaboration, and other use cases we haven’t even considered yet

Categories
links

Links

  • Constant work builder’s library pattern: Certain aspects of route 53 and the ELB control plane have been designed such that they are always doing the amount of work that would handle peak load. They can reduce variance in a system this way (they also have to understand limits well and use cells to partition traffic to keep individual clusters within these limits)

Categories
links

Links

  • The Case for and Against Cognito: Building a user management and authentication system can be hard. (User directory, identity provider federation (SAML), …) 3rd parties can help out quite a bit here. Discusses Cognito pros, cons, and sources of confusion
  • Stuck? Do Something!: Timely post by Jamis Buck. I feel anxious when I’m asked to do something I haven’t done before, or solve a problem that’s new to me. A reminder to take a breath, and pick something to start on. It’s ok if what I try won’t work. I’ve learned something and probably have another experiment waiting in the wings because of it

Categories
links

Links

  • Async task framework design doc from dropbox: Nice discussion of the design of their job scheduler service. At least once execution, priorities, no concurrency, guaranteed start times for most jobs at a scale of 10,000 jobs per sec (at least at time of writing)

Categories
links

Links

Categories
links

Links

  • Post incident report from Twilio for Feb 26, 2021 incident: Nice writeup with aggressive, hopefully impactful action items. A critical path service was discovered post incident response with insufficient capacity and autoscaling behaviours. When it went down dependent services followed. Dependencies were built to handle a failure from this upstream service

Categories
links

Links

  • Base64 encoding overhead is about 33%: The idea is to take a sequence of bytes and to make them safe to transmit over http or some other text based messaging protocol. To do this, base64 takes 3 bytes of binary data and turns them into 4 ascii bytes