State Management [coach]

posted in: architect, Design, Standards | 0

Avoiding spaghetti code or the big ball of mud.  We talked about breaking up our code into a sensible module structure, but that alone is not enough. There are a number of patterns that we can use to improve our code architecture. One area we need to consider and agree on is state management.

If we think about the ITE way… what are our current patterns for managing:

  • Application Objects and Values
  • Application Modes

Do we recognise any consistent patterns like:

Links:

https://github.com/ifandelse/machina.js

https://github.com/postaljs

Problem: State Management

Pick a problem to work on. Watch how the team works. What needs to be improved?

Options:

Consider your options. What could you try that might influence the situation for the better? List at least three options.
Experiment:

Pick one option to try.
Review:

Review the outcome. Did you improve things? Even if things haven’t improved, have you learned something?

Leave a Reply