vault backup: 2024-10-01 13:49:31

This commit is contained in:
2024-10-01 13:49:31 -05:00
parent 5a2d29f9bb
commit 8894a611ed

View File

@@ -11,7 +11,7 @@ Seems familiar with Visual Studio. Able to explain his basic plan to get going:
Interesting choice: adding "NeighborCount" on the cell model--should the cell model know about its neighbors? Interesting choice: adding "NeighborCount" on the cell model--should the cell model know about its neighbors?
IN progress: ahs not initialized the Board property yet--how will he discover this? IN progress: ahs not initialized the Board property yet--how will he discover this?
Got NRE when he ran this. easily found that he missed initializing Got NRE when he ran this. Easily found that he missed initializing the BoardGame property, explained why it threw well. Struggle a little to initialize the multi-dimensional array correctly.
Questions: Questions:
1. Can you GridSize everywhere to avoid errors? 1. Can you GridSize everywhere to avoid errors?
@@ -19,6 +19,7 @@ Questions:
3. Instead of a `(Row, Column)` comment, is there another way we could label the values? 3. Instead of a `(Row, Column)` comment, is there another way we could label the values?
4. Is there a way to calculate the coordinates of the surrounding cells without statically constructing a list of offset pairs? 4. Is there a way to calculate the coordinates of the surrounding cells without statically constructing a list of offset pairs?
5. You iterate through all cells in the board multiple times. Can you extract that logic to reuse wherever needed instead of copying it? 5. You iterate through all cells in the board multiple times. Can you extract that logic to reuse wherever needed instead of copying it?
6. Can he explain why using GridSize at the property initialization level doesn't work? He couldn't explain it--he needed a const or static integer for `GridSize` instead of a readonly class field. Opted to initialize the property at the top of the constructor.
Nits: Nits:
1. Property, field and variable naming not consistent 1. Property, field and variable naming not consistent