Wow, I found those refactoring tips pretty unique, and the way everything falls naturally into place near the end was so satisfying. I also had some fun trying to replicate this in Java although initially in a kind of not-Java way that would look as similar as possible to what you showed. You did a great job as always, I can't wait for the next part and eventually any new kata you manage to find.
Thanks, that's great news. I'll be looking forward to it and I'm eager to see how the refactorings can be improved even further with the power of object-orientation and classes.
Hi Emily, can you provide a link to the commit message notation you're using? Specifically, I want to know what the difference between "R" and "r" is when you're doing a refactoring commiit. I vaguely remember reading an article about this but can't remember enough to search for it. TIA
Hi Emily. In jetbrains products you can use ctrl+shift+arrows to move a function up and down without "jank-and-paste". Pretty sure Fleet and most other editors have similar features.
Thanks - you're right I could have used that. I didn't like the way it moved it one line at a time through the middle of the rest of the code though - it was difficult to see when I'd moved it to the place I wanted it.
@@EmilyBache-tech-coach I've started using this notation and I must say, it's very helpful when I'm sifting through my commit logs and trying to find something. One thing I'm finding a little hard to stick with is the tense of the commit message. I'm used to using past tense (?), e.g. "Added/Changed/Refactored" instead of "Add/Change/Refactor". It's not a biggie but I end up with some niggling inconsistency in the commit messages -- I know, it's bordering on compulsiveness. Thanks again for the learning.
Wow, I found those refactoring tips pretty unique, and the way everything falls naturally into place near the end was so satisfying. I also had some fun trying to replicate this in Java although initially in a kind of not-Java way that would look as similar as possible to what you showed. You did a great job as always, I can't wait for the next part and eventually any new kata you manage to find.
Glad you found it helpful! I'm working on a Java version of this kata, it's going to be published later in the year, so watch out for that!
Thanks, that's great news. I'll be looking forward to it and I'm eager to see how the refactorings can be improved even further with the power of object-orientation and classes.
Thank you for bringing Fowler's book to life. Bravo!
Thanks!
Hi Emily, can you provide a link to the commit message notation you're using? Specifically, I want to know what the difference between "R" and "r" is when you're doing a refactoring commiit. I vaguely remember reading an article about this but can't remember enough to search for it. TIA
It's Arlo's commit notation github.com/RefactoringCombos/ArlosCommitNotation. R indicates more risk than r.
Hi Emily. In jetbrains products you can use ctrl+shift+arrows to move a function up and down without "jank-and-paste". Pretty sure Fleet and most other editors have similar features.
Thanks - you're right I could have used that. I didn't like the way it moved it one line at a time through the middle of the rest of the code though - it was difficult to see when I'd moved it to the place I wanted it.
@@EmilyBache-tech-coach I've started using this notation and I must say, it's very helpful when I'm sifting through my commit logs and trying to find something. One thing I'm finding a little hard to stick with is the tense of the commit message. I'm used to using past tense (?), e.g. "Added/Changed/Refactored" instead of "Add/Change/Refactor". It's not a biggie but I end up with some niggling inconsistency in the commit messages -- I know, it's bordering on compulsiveness. Thanks again for the learning.