Blog
Financial institutions and other FinServ and FinTech companies are spending more than ever building applications for web, mobile, kiosk and even in-branch experiences. It’s encouraging to see the dedication of resources to this area, but the spending is spiraling out of control, becoming frivolous, and, in some cases, redundant.
Here’s a daunting task: deliver best-in-class digital services while reducing operating costs. Leadership teams are all too familiar with having to find innovative solutions to business problems while maintaining the integrity of consumer data, abiding to budgets, and operating within the constraints of the banking industry, one that is highly regulated and historically opaque when it comes to transparency.
A common refrain in tech companies today is: “I’d love to hire her, but she’s just not at the level we need.” This sometimes reflects a double standard, but not always. The reality is that while more women are taking up programming, many are often self-taught or graduates of code school bootcamps. They’re entering the workforce with drive and talent, but without the technical and professional support that’s much needed by employees who are not only new to the industry, but actively marginalized within it.
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.