Todo

Model: seven forms of waste in manufacturing (src: Book_ This is LEAN - Niklas Modig & Par Ahlstrom)

What does a good scrum master do? Teams private assistent Schedule meetings Work at the team boundary Know the trust level and relationship with the infrastructure team Know the dependencies’ owners relationship level Know the users / depending teams relationship level Help solve conflicts between teams Work on team Build trust Facilitate meetings Alignment Help solve conflicts in the team Dev vs Scrum master Dev = focus, sprint goal Scrum master = improve teamwork

01 Get Unstuck 02 Master My Stories 1 03 Master My Stories 2 04 Start with Heart 05 State My Path 06 Make it Safe 07 Learn to Look 08 Seek Mutual Purpose 09 Explore Others’ Paths 10 Move to Action steps: use them in order tools: use when situation calls for it models Model: crucial conversation Model: fool’s choice Model_ CPR Model_ path to action Model: downward spiral Model: fact vs story Model: types of story [[model-clever-stories....

(Book_ Release It! - Michael Nygard) Part 1 - Create Stability Ch2 case study Ch3 Stabilize your system Ch04 Stability Anti-patterns Ch05 Stability Patterns Part 2 - Design for production Ch06 case study Ch07 Foundations Ch08 Processes on Machines Ch09 Interconnect Ch10 Control plane Ch11 Security Part 3 - Deliver your system Ch12 Ch13 Ch14 Part 4 - Solve Systemic Problems Ch15 Ch16 Ch17 Model: cap theorem Model_ OSI model...

small set of instances that get the new build first. For a period of time, instances running the new build coexist with instances running the old build If the canary instances behave oddly, or their metrics go south, then the build is not rolled out to the remaining population todo: ref handling versions - peaceful side-by side running of different versions (src: Book_ release it! - Michael Nygard)

(Book_ This Is Lean - Niklas Modig) TL;DR Lean means valuing flow efficiency over resource efficiency Choosing for lean operations is a strategic choice with pros and cons. Maybe also Lean means valuing continuous small improvements over one big improvement. That continuous improvement is aimed towards the (impossible) ideal of 100% flow efficiency AND 100% resource efficiency. But favors flow efficiency, so it will focus first and focus more on flow efficiency....

Model_ resulting - decision quality vs decision outcome Learn what 20% or 30% chance of failure actually is like. Reminds me of investing advice from option traders: “whatever you do, make sure that you can still continue the next day” - Nassim Taleb’s books Model_ how beliefs are formed

https://udemy.com/course/oauth-2-simplified bad: implicit flow → everything passes through url bar (aka front channel) through ‘front channel’ aka address bar good: back channel (aka HTTPS between browser & server → AJAX js call) client id client secret (aka client password) flow app builds url to redirect user to the auth server scope redirect uri client id login & approve & redirect back authorization code one-time-use short expiration date only usable once app contacts auth server authorization code client secret alternative to “authorization code” flow (when no client secret - aka public client) PKCE - Proof Key Code Exchange...

I have found multiple ways of looking at this: behaviour vs methods behaviour vs state behaviour vs implementation (1) Unit-Test Behaviour, Not Methods focus on the features that the object under test should provide, We need to know how to use the class to achieve a goal, not how to exercise all the paths through its code. Describing Behavior, Not API Features We need to know how to use the class to achieve a goal, not how to exercise all the paths through its code....

Quote: Walking skeleton definition A “walking skeleton” is an implementation of the thinnest possible slice of real functionality that we can automatically build, deploy, and test end-to-end. -- Alistair Cockburn (src: Book_ Growing Object Oriented Software, Guided By Tests - Steve Freeman & Nat Pryce) (origin: [Cockburn04]) keep the skeleton’s application functionality so simple that it’s obvious and uninteresting For example, for a database-backed web application, a skeleton would show a flat web page with fields from the database....