In groups of two or three, perform a code review in move_car.py. Do your best to analyze not only the logical validity of the code, but the style, cleanliness, and maturity of it. Are there any obvious bad practices at play? Collect your thoughts and be ready to discuss.
I have a grid and a class Vehicle, which will have starting point(X, Y) on the grid, and direction(one of N,E,S,W) taken from user and there will be commands, L & R turns the vehicle 90 degrees around left and right respectively and M moves the vehicle one unit to faced direction.
For instance, if the command is M and the current direction is E, the vehicle moves from (x,y) to (x+1,y) and preserve its direction.
If the command is R, and the current direction is E, vehicle preserves its position but direction changes to S.
My input consists of 5 lines:
- The first line defines the limits of the grid;
XandYseparated by space - The second line defines the current position and facing direction for the first vehicle;
X,YandDirare separated by space - The third line defines the commands for the first vehicle, which is a line of string
- The fourth and fifth lines are the same as second and third except they are for the second vehicle
Note: Vehicles are sent sequentially. If the second vehicle attempts to move to the occupied spot of the first vehicle, the command will be skipped. If any move command makes any of the vehicles move out of the grid, that command will be skipped as well. Inputs are always in expected style, so there is no need to validate inputs.