So, the beginning and end of SOOJS was to address the following issues:
- Code maintainability (usually by others)
- Allow for segmented testing and change controls
- Be used in any project as much or as little as desired
Now, let me tell you, what you will see looks very simple (and is, by design) but it took a long time and many failed attempts to define a pattern that truly facilitated all of these concepts.
And as a simple aside here, it is this where SOOJS gets its name:
There is no magic, it’s just “Soooo JS”.
So, now that you know a little about the concept of SOOJS, take time to read through the next few topics to get a better grip on what SOOJS is trying to do for you.
I will attempt to organize the content so that you can bail at any time and still have some take-away. But understand that a pattern is only as good as someone’s firm grasp as to why it works in the first place. I will be going through many of the elements in the pattern in detail so you get a very clear understanding of why things are the way they are. If you like to skim or want to bail early understand that you will likely run into trouble when you try to apply the pattern.
Enough boilerplate, time to dive right in…