Published

https://martinfowler.com/articles/is-tdd-dead/ Other notes Article_ TDD is dead. Long live testing. - David Heinemeier Hansson Video_ Is TDD dead_ 1_ TDD and Confidence [[video-is-tdd-dead-1-tdd-and-confidence.md|]]Video_ Is TDD dead_ 2_ Test-induced design damage [[video-is-tdd-dead-2-test-induced-design-damage.md|]]Video_ Is TDD dead_ 3_ Feedback [[video-is-tdd-dead-3-feedback.md|]]Video_ Is TDD Dead_ 4_ Costs of Testing [[video-is-tdd-dead-4-costs-of-testing.md|]]Video_ Is TDD dead_ 5_ Answering Questions

https://dhh.dk/2014/tdd-is-dead-long-live-testing.html http://www.rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdfPaper_ Why Most Unit Testing is Waste - James O Coplien Video_ Writing Software - David Heinemeier Hansson

Agile is Dead - Pragmatic Dave Thomas https://www.youtube.com/watch?v=a-BOSpxYJ9M ruby community has pushed forward testing more than any other - culture of testing - experimented with lots of forms - frameworks -> 100% now you MUST have it or they don’t value you

Code as Risk • Kevlin Henney https://www.youtube.com/watch?v=YyhfK-aBo-Y Article_ Goto Fail, Heartbleed, and Unit Testing Culture - Martin Fowler Article_ Top 10 Secure Coding Practices 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 Article: Top 10 coding practices

DDD & Microservices: At Last, Some Boundaries! • Eric Evans https://www.youtube.com/watch?v=yPvef9R3k-M Context Map ac = anti corruption layer arrows indicate power, not data flow

Eric Evans — Tackling Complexity in the Heart of Software https://www.youtube.com/watch?v=dnUFEg68ESM specific, complex, important problems Modelling Paradigms Object Oriented Event Sourcing Relational Functional Graphs Logic / Rules engines

Is TDD dead? 1: TDD and Confidence https://www.youtube.com/watch?v=z9quxZsLcfo 3 things that bother me What is a unit test can’t have colaborators can’t touch db, file system fast, <1s -> no use out of unit tests that don’t talk to colaborators Driving arch through mocks mock heavy&enabling arch testing induced damage “Unit testing all the things” Red-Green-Refactor sometimes it works sometimes it does not work === What is a unit test KentBeck output tape, input tape, then build it personality, anxiety test-first appeared later...

Is TDD dead? [Part II] (test-induced damage) https://www.youtube.com/watch?v=JoTB2mcjU7w and it got there one test at a time one design decision at a time TDD puts evolutionary pressure on a design testability puts pressure on a design question of grain-size continuum of granularity of tests cost of every layer of indirection TDD is addicting No, desire for isolation is causing this result. isolation is the driver you cannot isolate yourself from backend/db/in-memory/webservice how much are we willing to spend, to get how much decoupling cohesion vs coupling willing to suffer high coupling, so I can have high...

Is TDD dead? [Part III] (feedback) https://www.youtube.com/watch?v=YNw4baDz6WA === Kent Feedback instant feedback is not always possible how far can we? how frequently feedback? 100ms – minutes fidelity of feedback green + prod -> % no crash different kinds of software different personalities overhead lifespan years & probabilities === Martin there is more than one thing you want feedback on User needs “is this software doing something useful for the user?” “how do I want to visualise the UI”...

Is TDD Dead? 4: Costs of Testing https://www.youtube.com/watch?v=dGtasFJnUxI === David other half of trade-offs things are not free pressures and nudgings over-testing “never write a single line of prod code without writing a test” multiples of lines of test code per prod code what is the right ratio? how many 9’s ? === Kent delta-coverage how much does a test test which none others do if you have multiple tests covering one behaviour, you have coupling...