12:37 Wunderbar ✨ Love your refactoring videos. I appreciate your very structured approach on refactoring. I've used to get stuck trying to refactor to much at the same time. I've been watching your videos for a long time now and have read the book a while ago, both of which helped me in improving my own refactorings over the years. Thank you for that. Even though we had some areas of code where context receivers deemed a great fit over the last years, we refrained from using them as they were still experimental. While the refactoring does not look to bad, I'm still glad we opted for that approach, as some of the contexts might've span almost the whole application, which in turn would've resulted in refactorings affecting a lot of places in the code. Of course a flexible startup like Gilded Rose can take some of those risks associated with adopting experimental technologies. 😉 Have a great weekend.
Thank you for your kind words. As you say, contexts are solving multi-layer propagation, and so require intervention at each layer. I’m thinking of reverting most of this refactor in order to redo it when context parameters are finally available (skipping a compiler version).
Thanks Duncan. It was very interesting to follow your reasoning. I also really like your plugin that tracks the progress of the tests and the shortcuts used. Which plugin is it, please?
Glad it was helpful! The shortcuts are shown with plugins.jetbrains.com/plugin/7345-presentation-assistant-for-2023-2, although I note that the IDE now has that built in (in a more in-your-face way). I get lots of questions about the test progress bar. It was written by the inimitable @dmitrykandalov. To use it install his Liveplugin (plugins.jetbrains.com/plugin/7282-liveplugin) and then this gist gist.github.com/dmcg/1f56ac398ef033c6b62c82824a15894b
Late this week as I was having so much fun at SoCraTes Belgium that I forgot it was Friday!
12:37 Wunderbar ✨
Love your refactoring videos. I appreciate your very structured approach on refactoring.
I've used to get stuck trying to refactor to much at the same time. I've been watching your videos for a long time now and have read the book a while ago, both of which helped me in improving my own refactorings over the years. Thank you for that.
Even though we had some areas of code where context receivers deemed a great fit over the last years, we refrained from using them as they were still experimental. While the refactoring does not look to bad, I'm still glad we opted for that approach, as some of the contexts might've span almost the whole application, which in turn would've resulted in refactorings affecting a lot of places in the code.
Of course a flexible startup like Gilded Rose can take some of those risks associated with adopting experimental technologies. 😉
Have a great weekend.
Thank you for your kind words.
As you say, contexts are solving multi-layer propagation, and so require intervention at each layer.
I’m thinking of reverting most of this refactor in order to redo it when context parameters are finally available (skipping a compiler version).
Thanks Duncan. It was very interesting to follow your reasoning. I also really like your plugin that tracks the progress of the tests and the shortcuts used. Which plugin is it, please?
Glad it was helpful!
The shortcuts are shown with plugins.jetbrains.com/plugin/7345-presentation-assistant-for-2023-2, although I note that the IDE now has that built in (in a more in-your-face way).
I get lots of questions about the test progress bar. It was written by the inimitable @dmitrykandalov. To use it install his Liveplugin (plugins.jetbrains.com/plugin/7282-liveplugin) and then this gist gist.github.com/dmcg/1f56ac398ef033c6b62c82824a15894b