Everyday Design Improvements in OO Code | Guided Learning Hour

Refactoring tools these days are very good. And most developers don’t make good use of them. We refactor code in order to improve the design and make the code easier and cheaper to modify. Tools make it quicker and safer to refactor. I want to help your team to experience that. Today’s design improvement replaces several longer, more complex methods with shorter, simpler methods. We’re going to practice ‘replace conditional with polymorphism’.

This video is a Guided Learning Hour. It's designed to be done together with your development team, although you can watch for yourself too.

The last part of the video is the session briefing. Watch this part to help you prepare to lead this session with your team. You can also find out more in my "Guided Learning Hour: How-to" video.

▬ Links ▬▬▬▬▬▬▬▬▬▬
How to use this video: ➡️    • Technical Coaching: Software Team Tra...  

You can find the code for the exercise on my Github ➡️ https://github.com/emilybache/Parrot-...

If you like this content and want access to a copy of the activity board, you can get it via Patreon ➡️   / everyday-design-improvements-in-oo-code-15...  

Emily on social media
LinkedIn ➡️   / emilybache  
Mastodon ➡️ https://sw-development-is.social/@emi...

▬ Video chapters ▬▬▬▬▬▬▬▬▬▬
00:00 - Introduction
00:54 - Gather your team
01:11 - Connect: Fill in the blanks
02:21 - Concept: Refactoring - a part of programming
04:10 - Demo: Parrot Refactoring Kata
13:41 - Concrete Practice: Parrot
15:05 - Conclusions: Collect viewpoints
15:36 - Closing words
16:02 - Session Briefing