So recently I have been developing a Sudoku Solver program that would go through a bunch of algorithms and determine the answer. Anyways I was getting pretty far developing more advanced algorithms to solve it faster and eventually was able to solve hard puzzles on websudoku.com. The problem was that it was all jumbled together in one massive class.

This of course was a problem for me that liked order and nice design in my programming projects. My next task was to take what I had and translate it into an object oriented system. I created objects for rows, cols, boxes. A puzzle to that included all the rows, cols, and boxes. I also created a Line object which was an abstract representation of rows, and cols. I then set about creating different types of data in them that I would need like what used numbers were in each etc. It was great but when I started to implement my algorithms I found more and more things I could not do.

In a massive class I had ultimate control over the data arrays and could immediately grab anything via hardcoding it. With these new objects I had to implement a large group of methods to pass the need data that may only be used by one algorithm. This was unacceptable to me I want it to be dynamic so that I could grab it through simple methods.  Needless to say I continue to write my Sudoku program despite numerous hard to find errors dealing with data management and incorrect data. I have to constantly monitor what data I am getting since it appears to always being incorrect and not what i needed. None the less my new design is much more elegant.

I hope to have something on here soon with my Sudoku Solver working a first version of the much better designed one of course. It all depends on if I can figure out the errors I am getting right now.