learning-hours/learning-hour-maker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch 'main' of ssh://gitea.apps.sustainabledelivery.com:3022/learning-hours/learning-hour-maker

Browse Source
This commit is contained in:
Your Name
2026-09-28 21:59:04 +00:00
parent 679e95eb83 5bb8121592
commit 60b1a02ea4
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ideas/split-loop-with-lambda/zeroth-draft-of-refactoring-pattern.md
+2 -4
View File
@@ -1,12 +1,10 @@
# Authors: Willem van den Ende, Emily Bache
# Authors: Emily Bache, Willem van den Ende
# Introduction
For a client, Emily and Willem have done several Split Loop refactorings. We want to be explicit in naming the patterns, and ensuring that the team have sufficient memory to complete these on their own. In the final session we did Split Loop, but the type of variable that we did the 'slide statement' refactoring with was a function instead of a value. And the 'split' part of the lop that got sliced up was an iteration that resulted in a list of function invocations (if memory serves me write).
This is a zeroth draft. Our meta-goals are being more explicit in naming the refactorings and patterns we used to ourselves, so that the team can name the patterns, and reproduce the mechanics reliably on their own.
This is a zeroth draft. Our meta-goals are being more explicit in naming the refactorings and patterns we used to ourselves, and enable others to name the patterns, so they can reproduce the mechanics reliably on their own.
Initial literature survey (see related patterns below) has not yet revealed an existing Refactoring Pattern description. In order to fit some or all of this refactoring in a learning hour, it is worth writing down what we mean, with examples (so, in case the resulting exercise does not fit in a learning hour, we have a blog post to refer to for more details and/or recapturing the mechanics).