Published

cf: Tuesday of Model_ Design Sprint (src: Video_ The Future of Software Engineering - Mary Poppendieck)

start with signals, not requirements have a problem statement, not features plan with hypotheses, not estimates experiments around a hypothesis, not backlog of stories analysis and conclusion, not guesses analysis and conclusion, not guesses if you have good problem solving teams, what good are estimates? within constraints here is my constraints here is my problem (src: Video_ The Future of Software Engineering - Mary Poppendieck)

[planning] reflection every week know at beginning of the week reflect at end of week 3 outcomes / day & week gettingresults.com - Scott Hanselman (src: Video_ Scaling Yourself - Scott Hanselman)

(src: Video_ Scaling Yourself - Scott Hanselman)

The less you do, the more of it you can do. (src: Video_ Scaling Yourself - Scott Hanselman)

(https://vimeo.com/108441214) Paper_ waterfall - Winston Royce Paper_ Big Ball of Mud - Brian Foote, Joseph Yoder read: alan K Article_ Dr. Alan Kay on the Meaning of Object-Oriented Programming https://en.wikipedia.org/wiki/Alan_Kay read: Carl Huwitt https://en.wikipedia.org/wiki/Carl_Hewitt -> learn erlang to learn paradigm for better OO Video: The art of destroying software - Greg Young Greg Young - The art of destroying software Paper_ waterfall - Winston Royce You should read the original waterfall pater....

Dreyfus model Novice: needs rules best practices nothing else keep it simple Advanced beginner: test rules break rules test the limits Competent: applies rules has internalised Proficient: falls back on rules instinct, instinct, insight don’t trust it yet Expert: transcends rules no longer think in rules Dreyfus Squared novice + expert = x-( someone dies advance + advanced massive learning don’t put into prod competent + novice = :-) proficient + expert = :-D...

(src: Video_ How to Break the Rules - Dan North) (origin: Book_ Beyond the Goal - Eliyahu M. Goldratt)

Article_ Documenting Architecture Decisions - Michael Nygard OO = “little computers passing messages” Alan K replaceable component architecture Video: Software that Fits in Your Head - Dan North Software that Fits in Your Head - Dan North software is not the point productive != effective to getting the business impact understanding code code I know (new code no-one knows (middle) code everyone knows cared for...

Video: Software, Faster - Dan North Software, Faster - Dan North https://www.youtube.com/watch?v=USc-yLHXNUg patterns of effective delivery Jeff Sutterland talks about hyper performing teams from years to months PATTERN: repeatable strategy depends on context (vs best practice no context) has name context (where it works) warning (where it does not work) best practice -> novice design pattern book: != pattern idioms to get by in a crappy language EFFECTIVE: goal - what are we optimising for eg....