LIST
Model: 3 Axes of software development as opposed to functional and non-functional functional (runtime) operational (runtime) developmental (dev time) Refactoring = keeping functional axis stable eg. func fixed dev improves ops is kept open (src: Video_ Code as Risk • Kevlin Henney)
Hypothesis-driven delivery (src: Video_ Why Scaling Agile Doesn’t Work - Jez Humble)
ROI - cost estimates don’t matter prioritize based on cost of delay “how much would we have earned if this was in production” We’re more wrong than not in guessing which features will be valuable (90% wrong in uncertain/new markets, xx>50% in well known markets) So what do we do? (src: Video_ Why Scaling Agile Doesn’t Work - Jez Humble)
Different types of user research (src: Video_ Why Scaling Agile Doesn’t Work - Jez Humble)
Book_ 7 Languages in 7 Weeks - Bruce Tate [[book-7-languages-in-7-weeks-bruce-tate.md|]]Book_ The Language of Emotions - Karla McLaren Book_ The Art of Empathy - Karla McLaren Description Ryan Ripley (@RyanRipley) Amitai Schlair (@schmonz) and Arlo Belshee (@arlobelshee) covered one of the most diverse agendas ever covered on the podcast. We started with a discussion about scaling agile, the limitations of frameworks like SAFe, LeSS, and DaD. We then moved on to the limits that consistency puts on innovation and how tuning consistency can be a serious competitive advantage....
learn design by learning the language which makes a specific design trivial Audio_ AFH 016_ Are You Mocking My Unit Tests_
BDD Is Not About Testing - Dan North https://www.youtube.com/watch?v=6nSwRSbc27g model by Neil NIckeleison Polly Anny Pixton book build vs buy stakeholders: ppl - users - programmers (feature you) - PO - security - … “people whose lives you touch” increase confidence - subjective - depends on different ppl Article: TDD is not about testing nov 3 2003 (2) Original TDD explained book, white book, kent beck 4 values - simplicity - comm - feedback - courage...
Video: Stop Over-Engenering - Greg Young Video: Stop Over-Engenering - Greg Young https://www.youtube.com/watch?v=GRr4xeMn1uU Am I still on the happy path NOT what are all the things that can go wrong? Cost-Benefit-Analysis on everything When is my break even? Quote: Every software developer should pay another software developer
The hard part is: What problems are we gonna solve? Book: Sprint - Jake Knapp prototype and test any idea in 5 days before actually coding Video: Design Sprint Google IO 2014 (src: Video_ The Future of Software Engineering - Mary Poppendieck)