TLDR
Very little coding. Continuing to think through the Catan game flow and reconciling how a REST API could be designed to coordinate with the proposed Finite State Machine. Specifically, what kind of “actions” should the REST API allow, and how will the state machine handle those actions in a scalable and maintainable way.
Main work
- Brainstorming and working through game scenarios and edge cases.
- Reviewing REST API design best practices.
- Reviewing the rules and constraints of the Catan game.
Challenges
- There are probably a million ways to build the “business logic” of this system. We are largely leaning on personal experience to decide when we’ve reached an acceptable solution that isn’t over or under engineered.
Learnings
- It is worth spending time thinking about a wholistic solution early on, before you have tech debt.
- That being said, you can only toil with thought experiements for so long before you just have to get your hands dirty with some implementation.