Blog
Over the last year, two architectural ideas have risen to the surface of JavaScript web app development: Component-Oriented Architecture (COA) and Redux state management. Component-Oriented Architecture is one of the main tenets in both React and Angular: it encourages developers to break down the UI into a graph of self-contained, re-usable UI components. On the other hand, Redux is a functional-reactive approach to state management where the UI is at any time a derivation of a global, immutable store.
Any chainsaw that can cut down a tree can also take off a leg if used carelessly. Equally, any framework as powerful as Angular will inevitably contain traps for the unwary.
Building digital analytics features into web and mobile products is a small but strategically important set of activities when building out an MVP (minimum viable product) or rewriting a product. This blog post reviews where analytics planning intersects with other project kick off activities.
Programmers tend to have strong opinions about what makes code easier or harder to understand. Until recently, though, those opinions have been based on self-analysis and received wisdom, i.e., on programmers thinking about what they themselves do, and (more often) on what the rest of the herd is saying.
When delivering mobile and web applications that include analytics, it is important to gauge the organization’s current analytics capabilities and how the project can advance them.
On June 12, Doug Riches headed to London, England to present How JavaScript is Radically Changing The Way Financial Institutions Create Enhanced Customer Experiences Fostering Creativity to an eager audience at FinDEVr, part of London’s Tech Week. The Q&A portion was full of engaging questions, here’s some of the highlights:
DevOps is what happens when developers work hand-in-hand with the system administrators and other IT staff who are responsible for getting software into users’ hands and keeping it running. Discussion about it frequently centres on tools, but its core is a set of practices that are best understood as answers to a handful of key questions.
So many software development projects start with high levels of uncertainty. Some of it is explicit, you many not know exactly who the target customer is and what they want, and some of it may be implicit, you have a great idea but are uncertain about the technical risks of delivering the experience or what the state-of-the-art is capable of and, as they say, you don't know what you don't know. In these cases we echo the words of "Ike" Eisenhower: