At CTL, we've been using smoketest for several years now. It is a standard part of our stack now and has helped us prevent numerous issues from making it to production as well as simplified and sped up the identification and fixing of production environment issues.
The first MOOC course that I worked on was a three-part series based on the Civil War and Reconstruction taught by Professor Eric Foner. I've learned many valuable lessons on how to design an effective course using the edX platform. I gathered some best practices to share with others interested in creating MOOCs.
In second part of a the MATCH and PASS sustainability summary, we outline the solutions and development of the migration process, from framework choices for the sites to packaging JavaScript interactives.
In this first of a three-part summary, we recount the circumstances that drove the decision to migrate two dental school projects, MATCH and PASS, to an open and sustainable framework. We also listed a few questions that we must address before moving forward with the implementation.
This summer, we revisited client-side interactives that we built for online learning web applications, and bundled them using Webpack as JavaScript packages for open and wider distribution. We are proud to announce that we now have a portfolio site to showcase about a dozen standalone interactives that we've authored.
Here at the CTL, we are passionate about delivering high quality code that adheres to community standards. Our quality control arsenal includes unit tests, code reviews, static analyzers, style checkers, and continuous integration. Our recent adoption of webpack for JavaScript interactives required a fresh approach for unit and client-side testing complexities.
At the CTL we have about two dozen utility machines spread over 6 physical locations, as well as another three dozen or so staff laptops. Managing updates, user accounts, and printers for all these machines is not only a big job, but also one of many small repetitive steps—which makes it ripe for automation. Having been exposed to DevOps practices at the CTL, I wanted to find a way to corral all these machines in a sustainable way.
Go, a systems programming language developed and open sourced by Google, has emerged as a very important language for interesting infrastructure projects such as Docker and Prometheus. It's worth keeping a close eye on the Go community to stay updated on those kinds of projects. This post outlines how, where, and why we use Go at CTL.
This summer, we migrated two projects, MATCH and PASS, to a more open and sustainable framework. Openness and sustainability pose interesting challenges such as responsiveness and accessibility. We have committed ourselves to good faith effort in making sure that both sites perform well on all devices including assistive technologies.