Canopy

Why You Should do all Your Testing in Prod

Testing in prod? As developers we typically run a local version of our application with fake data to preview the changes we’re making as we develop before we deploy them to production. But what if you could run your app in production with pieces of it being loaded from your local machine? Then you could develop against real data and production. Also, you wouldn’t need to run the entire back-end stack while making only front-end changes.

Thoughts on Microservices

The programming world moves very quickly compared to other industries. Many things come and go and it can often be hard to keep up with the latest trends. More often than not, it makes sense to not follow common trends, as they are untested, and might fade in a couple years anyways. How do we decide which trends to follow and which to pass on? This is a really hard problem, but can often be decided by digging further into the trend.

Canopy's Sponsorship of SystemJS

Open-source Software Canopy is a SaaS product for tax professionals built upon a variety of open-source technology. When a project is open-sourced under a permissive license that means anybody can view, use, modify, and distribute your project for any purpose (https://opensource.guide). Open-source technology is built and maintained by hundreds and thousands of developers who may each contribute hundreds or even thousands of volunteer hours. While the success of most modern software companies is dependent upon a collection of open-source software, open-source development is often a difficult and thankless task.

A step-by-step guide to single-spa

Running Angular 1, React, Angular 2, and Vue.js side by side sounds pretty cool. And it seems appealing to have multiple applications coexisting on the same page, each lazily loaded. But using single-spa for the first time can be tricky because you’ll come across terms like “application lifecycles”, “root application”, “loading function”, “child application”, and “activity function.” This blog post will take you through setting things up and what choices you have when using single-spa.

A Case for SOA in the Browser

So you are a web-developer. You write a lot of JavaScript. You have a large single-page application (SPA) with features to add and bugs to maintain. Over time the application grows in size and complexity. It becomes more difficult to modify one portion of the SPA without breaking another portion. The company is growing and you are looking for ways to scale the team and code-base. You add unit tests.