Advertisement
.NET Fest 2018. Nathan Johnstone. Dealing with Medusas in your Codebase
Report
NETFestFollow
Oct. 29, 2018•0 likes•241 views
0 likes
Be the first to like this
Show More
views
Total views
0
On Slideshare
0
From embeds
0
Number of embeds
0
Check these out next
.NET Fest 2018. Nathan Johnstone. Dealing with Medusas in your Codebase
Oct. 29, 2018•0 likes•241 views
0 likes
Be the first to like this
Show More
views
Total views
0
On Slideshare
0
From embeds
0
Number of embeds
0
Report
Education
Existing software systems can be hard to change, and handling the complexity as you try to implement a new feature or bug fix is often a nightmare. The Mikado Method is a structured technique that lets you deal with the demons that are unleashed by breaking changes into small manageable pieces. After an overview of the technique and its steps, we will go through a small kata demonstrating how to start applying it
NETFestFollow
Advertisement
Advertisement
Advertisement
Recommended
Chef boston-workflowsPete Cheslock
RUC 2003 reducing time to market using follow-the-sun techniques AlexanderCameron11
Constraint Programming - An Alternative Approach to Heuristics in SchedulingEray Cakici
Legacy code - Taming The BeastSARCCOM
July 29: Achieve Stakeholder Alignment on Governance: Navigator by Pivotal LabsVMware Tanzu
Tetap Agile dengan Arsitektur Monolith - Ziya El AriefDicodingEvent
.NET Fest 2018. Nathan Johnstone. Dealing with Medusas in your Codebase
- Dealing With Medusas in Your Codebase Applying the Mikado Method Nathan Johnstone - Chief Architect @ Omnia Retail
- Focus
- A Bit About Me ...
- New Zealand
- Antartica (Almost)
- Antartica (Almost)
- No Hobbits or Dwarves
- Or Are There ?
- A Bit About Me ...
- A Test ...
- Pigs != Pegs
- Story of a Code Change
- The Battle
- Broken Code
- Let's Get Down To Business
- Git Commit Trail
- Final Result
- A Better Way...
- Layman's Terms
- 100 Mile View
- Cognitive Limits
- Set a Goal
- Experiment
- Visualize
- Undo git reset --hard
- Advantage - No Refactoring Branches
- Advantage - Faster Progress
- Advantage - Mapping
- Advantage - Intentional Programming
- Advantage - Collaborative Refactoring
- Advantage - Visibility for Large Changes
- Advantage - Higher Quality Code
- An Example - Pasta Software MasterCrüpt (TM)
- New Customer - Stranger Eons Ltd
- Share The UI
- Warning Live Code Demo Ahead ! Warning Live Code Demo Ahead !
- Takeaways ● Mikado Method provides a structured approach for implementing technical changes ● Divide and conquer ● Works for individuals and group wide technical changes ● 4 Steps - Set a Goal -> Experiment -> Visualize -> Undo ● Unlocks continuous integration and deployment for complex changes
- Links ● https://www.manning.com/books/the-mikado-method ● https://github.com/mikadomethod/kata-dotnet ● http://psychclassics.yorku.ca/Miller/
- Questions ?
Advertisement