Video: The Future of Software Engineering - Mary Poppendieck
April 7th, 2019
(https://www.youtube.com/watch?v=6K4ljFZWgW8)
[ ] Book: Antifragile - Nicolas Taleb
[ ] Paper: Resilience Engineering: Learning to Embrace Failure - Acm Queue
[ ] Book: The DevOps Handbook - Gene Kim, Jez Humble, Patrick Debois, John Willis
[ ] Book: Continuous Delivery - Jez Humble, David Farley
[ ] Paper: Online Experimentation at Microsoft - Kohavi, Crook, Longbotham
[ ] Paper: Standis Group Study Reported at XP2002 by Jim Johnson, Chairman
[ ] Book: Sprint - Jake Knapp, John Zeratsky, Brad Kowitz
[ ] Video: The Design Sprint - Google I/O 2014
1) scale out
more servers
CAP theorem
less communication
autonomous teams
2) infrastructure as code
conway's law: org structure == architecture
autonomous teams: independent deployment
ops: self-service
there is a cloud in your future
cheaper
more stable
more secure
more expandable
infrastructure as code
containers
serverless = event-driven
software-defined-networks
3) The New Technology Stack
dependency problem
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/2d926bfe-0209-4f57-9215-5d3b993d5030/5f5e6c65012419b0f5e1174e0c00def0/screenshot.png)
api > db
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/e1765d2b-14ad-4278-9a82-f533c78625b6/d96bde32253673e68c9b1cf8d36fa506/screenshot.png)
big data
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/a4ca563f-1616-4a24-8c6d-a61c28d7c8a5/c776f7ed885c8084e82ac835fbc95566/screenshot.png)
resilience engineering
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/f5172211-ca0e-42a5-9436-102f107b520b/ce78e11fe30f33e30a6d3f7f00e5a339/screenshot.png)
Book: Antifragile - Nicolas Taleb
Resilience Engineering: Learning to Embrace Failure - Acm Queue, September 2012
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/12bf9082-7ff0-49db-af1c-0d0329da0f04/f5d60c77c4c8e206c229b8e42257ecd0/screenshot.png)
===
Devops
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/6de6bb5c-5974-4bc7-9f31-376dc60b0759/35d55f5a997d5aad572db3641a08c4c0/screenshot.png)
Book: The Devops Handbook
Flow
Feedback
Experimentation & Learning
1) Flow
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/3bda3f67-d77e-4a45-a6c7-f1667f7f0c39/9ca196dac2ffafac90477ee29d40dd59/screenshot.png)
Book: Continuous Delivery - Jez Humble, David Farley
deploy all the time
release is flipping the switch
2) Feedback
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/fe5d94be-9d3d-49c0-a2e4-fdc0e51006c6/638ac275833a8e1e7dcdadbe29706104/screenshot.png)
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/8f2ed131-40ac-45dc-b867-77895cb7c812/6b83aebbc821758a5c8cb2d62cff4fd6/screenshot.png)
Paper: Online Experimentation at Microsoft - Kohavi, Crook, Longbotham
Paper: Knowledge Discovery & Data Mining - exp-platform.com/expMicrosoft.aspx
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/5e5d0015-f74d-40b3-ad1f-6d2f2ee9dc99/8732ccc93595df3dcc56e74372ddaf80/screenshot.png)
Paper: Standis Group Study Reported at XP2002 by Jim Johnson, Chairman
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/4e9c25d2-547f-4b15-94cd-232bc4b05dbc/748405c7777f7d9f2974c1dccdb81060/screenshot.png)
3) Experimentation & Learning
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/49e6d8a2-8e90-432d-a6ce-79abbcb4e0ab/71370e91db8f69cc48c6bd2b1f2d9526/screenshot.png)
start with signals, not requirements
have a problem statement, not features
plan with hypotheses, not estimates
if you have good problem solving teams, what good are estimates
within constraints
here is my constraints
here is my problem
experiments around a hypothesis, not backlog of stories
analysis and conclusion, not guesses
The hard part is:
What problems are we gonna solve?
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/ca8ece15-8753-40e2-954e-d380d4bbe29f/af85392f3322fc6b1f12005d68ca381d/screenshot.png)
Book: Sprint - Jake Knapp
prototype and test any idea in 5 days
before actually coding
Video: Design Sprint Google IO 2014
idea generation (Tuesday)
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/cc06f559-ed9b-4711-8f62-ff6d50ceff21/2ed27317d76ceaabb0da766945f72259/screenshot.png)
Conformity Bias
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/9fe7a6df-4645-421b-859b-4299b818f6d8/33092d79c00da9015694a1d73446fe20/screenshot.png)
Wednesday: they vote
-> don't like
-> needs majority
-> Attract people to ideas
if you can attract a few ppl to an idea
===
SUMMARY
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/bef58595-dc38-42e5-b137-d75b151998ca/56f0d658d9a983517731a1674e906ae0/screenshot.png)
===
Q&A
Site: www.poppendieck.com
Trend away from monolith and towards distributed systems.
Try and solve problems they don't have.
Over-engineer solutions.
-> Speed of learning
-> Need to migrate
-> Find your own solution
hadoop took 8 years
amazon took 5 years
if you wanna do it in 6 months, you're crazy
What do you think about the role of regulation systems like laws and government in the cloud federated world.
-> there will be regulations
-> cloud ppl better figure it out
-> cloud can be in many different places, and the location where will change rules
This post was referenced in: