Reduce Method Sprawl with Code Paragraphs | Software Team Learning

54 года назад

9,813 Просмотров

▬▬▬▬▬▬▬▬▬▬ This video is sponsored by Tuple: https://tuple.app/emily ▬▬▬▬▬▬▬▬▬▬
Learn about step three in Naming as a Process - Split into Chunks. We'll use code reading techniques to identify then extract paragraphs. This session is 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.

The idea is that any technical coach or developer with an interest and some facilitation skills should be able to lead this session with their team, with a little preparation. It could be a good way to promote useful discussions in your team.

▬ Links ▬▬▬▬▬▬▬▬▬▬
How to use this video: ➡️ https://youtu.be/7dnKYg4lkzI

More information about Naming as a Process ➡️
https://www.digdeeproots.com/articles/on/naming-process/

You can find the code on my Github ➡️
https://github.com/emilybache/Yatzy-Refactoring-Kata

If you like this content and want access to a copy of the activity board used in this session, please join my Patreon ➡️
https://www.patreon.com/EmilyBache
or purchase materials for just this session ➡️
https://www.patreon.com/EmilyBache/shop/reduce-method-sprawl-with-code-activity-297894

Emily on social media
LinkedIn ➡️ https://www.linkedin.com/in/emilybache
Mastodon ➡️ https://sw-development-is.social/@emilybache
X (Twitter) ➡️ https://twitter.com/emilybache

▬ Video chapters ▬▬▬▬▬▬▬▬▬▬
00:00 - Introduction
01:40 - Connect: Why does code have long methods?
02:27 - Concept: Long methods have paragraphs
06:39 - Code Paragraphs sparrow deck
11:46 - Code Paragraphs theory and exercise
13:46 - Demo Paragraph to method
19:14 - Exercise instructions
19:46 - Conclusions
20:40 - Session Briefing

Тэги: