Reimagining Cobalt.js preferences in AngularJS using UML
_, and (gasp) synchronous XHR requests so our APIs could avoid callbacks.
Here’s a representative look at how WestlawNext accessed preferences from the browser:
If I was coding something similar today using features of AngularJS, it would look more like this - utilizing Dependency Injection and $q for Promises.
Aside from critiques on my diagraming skills, what are your thoughts on UML vs. code snippets to communicate with other developers?