anomaly2104 / chess-low-level-system-design

Repository contatining the low level system design of Chess.

Low Level Designs:

Topic	Video
	https://youtu.be/7IX84K9g23U
	https://youtu.be/Yn7C0x5ozx4
	https://youtu.be/RVHNcng0oF0
	https://youtu.be/B7iCXl_KSoM
	https://www.youtube.com/watch?v=WUhtVmHr0EM&list=PL564gOx0bCLp8Mqv3nlE8QP8UaX0hKkEA
	https://www.youtube.com/watch?v=Xny0IdvJ-1M&list=PL564gOx0bCLpAL7yMJqOuK3_hBuLkyRhn

Connect with me:

chess-low-level-system-design's Issues

Just some question.

The design is pretty good but
the design is pretty complex to be used in design interviews.
How much time did you take to design this system.

Also do you make Usecase diagram , class diagram or jump right into coding in machine rounds

Immutable Piece Move providers

Instead of explicitly mentioning/creating ImmutableList every time in Test Helpers while creating Piece. This should be the logic of Piece that is it should copy the passed PieceMove Provider and should not leak reference from the getter method also.
That is:

A parameterized constructor should initialize all the fields performing a deep copy so that data members can’t be modified with an object reference.

Deep Copy of objects should be performed in the getter methods to return a copy rather than returning the actual object reference)