If you're new here, you may want to subscribe to my RSS feed.
[fb-optin-form uid='' nofollow=false style='main' titletext='You can also get the feed via email. Sign up now by supplying your email address and clicking the Subscribe button' nonloggedonly=false]
I loved teaching this particular group because they were actively engaged in the material. So many times, when I teach, the students simply absorb what I say, but they don’t interact with it. They never ask the question, “What are the implications of what is being said.”
And while this technique is an outgrowth of my involvement with TDD, this particular technique can be used with or without TDD.
Long time readers may remember that I started using Ext JS about 3 years ago. At the time, I was using version 4.2.2. I recently started a new contract where they are using Ext JS 6.0.1. I have to say, this version solves a lot of the architectural issues I had with the 4.x series. But, there are still problems.
Since I’ve provided an evaluation of Angular 2 and React JS, I thought providing an evaluation of the current version of Ext JS would be appropriate since these three seem to be the main players in the corporate world.
Over the last couple of weeks, I’ve mentioned that I’ve been learning React JS. First in the article “Reaction to React JS and Associated Bits” and then last week in my article “Test Driven Learning”. In the first article, I mentioned that if you use React JS, you’ll probably end up using the Flux design pattern and since there are multiple ways of implementing flux, getting a clear definition of what it is and how it should work can be confusing. At least, I found it confusing.
And now that I’ve figured it out, I thought it might be helpful both to myself and to the programming community at large if I offered my own Explanation of the Flux Pattern. At the very least, it will give me one more way of solidifying the concept in my own brain. Maybe it will be helpful to you as well.