Read our latest articles on technology and the software industry. Our writers are experts who love to share their expertise, sometimes witty, sometimes insightful, always interesting.
Tech Stack Modernization Volumes 1 and 2 covered my thought process behind modernization and a review of Angular. Volume 4 will review my selected framework, (spoiler: it's Vue.JS), but before I get there I want to write a bit about Webpack and NPM. Both of these are tools that can be used with any tech stack (Angular, React, Vue.JS, etc.), and they bring their own benefits and pain! Webpack Webpack is a "module bundler," but I think of it … [Read more...]
When "Pull" is Insufficient Software developers live in a pull first world. Even modern single page applications (SPAs), while highly interactive and responsive, only respond to change when the client initiates it. A user sees a list of work orders, and the list doesn't update unless that person requests an update, either by refreshing the page, or performing a change of their own that initiates a full or partial reload of data from the … [Read more...]
This isn't a primer on Docker, containers, virtual machines, system resources, or anything like that. All of that has been written about extensively elsewhere. This is about getting local development environments up and running, fast. When I stumbled upon Docker, at first I thought it was something like Composer or NPM because I could "install with Docker." So, I looked it up: "Docker is an application build and deployment tool [that] can … [Read more...]
In Tech Stack Modernization, Volume 1, I discussed why I'm evaluating new clientside frameworks, and I listed my goals and requirements. You'll note that I prefer small focused libraries over kitchen sink frameworks, which is part of the reason I like Knockout.JS so much. Because of that preference, Angular was a bit of a tough sell for me, but after struggling with framework selection I decided to hold my nose and dive in! Disclaimer: … [Read more...]
How do you know when you need to take the considerable effort of choosing a new tech stack? There can be a number of signs: Finding new developers willing to work on your stack is getting harder. Newer stacks promise (and hopefully deliver) better performance, faster development or better user experience. Your current stack is preventing you from implementing the features or performance your users expect. You need to freshen your … [Read more...]