I want to do something similar in Java, so I aim to port this code to Java,
and trying to keep it as close to the original as possible - the good thing here is
that it consists of one method and one class only, so you can go from top to bottom through the code,
without having to click back and forth, which makes it a good fit for a live refactoring, I think.
I have ported most of the code, just the tough Linq bits are missing.
Lines 300-360 and 494-677 are specifically hard to port to Java.
Any help is greatly appreciated
Liutauras Vilda wrote:
What is missing in that video, that tests don't play any role in the refactoring process. You might wrote them and demonstrated how much confidence they add to refactoring?
Yes, I am planning to show/use tests... but, that is not really helping me at this point. First, I need a basis to start the refactoring from. I still think Sudoku could be a good use case - but
maybe the given C# code is too far away from Java, to hard to port. So now I am thinking about developing my own nasty procedural version of Sudoku.