Something I'm starting to realise about the approach to architecture

This has come up a few times, but it’s just started to solidify in my brain. The idea of building a system from the high level to the low level. Such as in the saving system, building the methods like CaptureState and RestoreState which deal with orchestrating the whole process of saving and loading, before any functionality that actually touches the actual getting and setting of data at the level of the SavableEntities.

Normally when I’m building a system like this I would start with the lower level stuff like the SavableEntity, and then build up from there. I’m wondering if this is just a difference of approach that is down to style, or if the method being used in these lectures is more often the better way. It’s definitely giving me a lot to rethink.

1 Like

Now that you mention, it makes a lot more sense starting from the high level for decoupling reasons, once you code the high level you can procede to attach it with as few lines of code as possible.

Thanks for the insight, I never realized that.

1 Like

Privacy & Terms