Mathis' opinion: I was a bit confused about how to occupy this class. Is it necessary? I can see the advantages to having a designated Move class, and as of now, I have been storing the move validation in the same spot, but putting it in Board would also make a lot of sense.
Claude opinion: Current Move conflates "represents a delta" and "validates itself" in the constructor. Research common patterns: should Move be a plain data object (from/to/capturedPiece), with validation living elsewhere (in Piece or Board)?
Mathis' opinion: I was a bit confused about how to occupy this class. Is it necessary? I can see the advantages to having a designated Move class, and as of now, I have been storing the move validation in the same spot, but putting it in Board would also make a lot of sense.
Claude opinion: Current Move conflates "represents a delta" and "validates itself" in the constructor. Research common patterns: should Move be a plain data object (from/to/capturedPiece), with validation living elsewhere (in Piece or Board)?