Throughout my career, I have worked on quite a few Angular projects. In this post, I will go through some of the different projects I have worked on and explain the lessons learned in each so you can learn from them. Ionic + Cordova mobile app with AngularJS (2015) This app was about creating an …
I just did this live talk at AarhusJS – a Javascript meetup in Aarhus (Denmark), my hometown 🙂 The talk extended upon the lessons learned after working with Angular monorepo projects and will teach you about: Creating a good Angular architecture Case study: Monorepo architecture Using Sandboxes/facades Organizing libs and conventions in a monorepo Enforcing …
In this blog post, I will cover why I went from using Protractor to start using Cypress for end-to-end testing. We will look at the flaws in Protractor and how Cypress is fixing them as well as looking into the 7 steps to Cypress e2e testing success. Let’s get started! If you have been working …
Why I Moved from Protractor to Cypress and the 7 Steps to Cypress E2E Testing Success Read More »
To be as efficient as possible on your Angular team you must realize that the process framework you are using has a bigger impact than the actual tools and technologies you are using. A common problem for engineers is that they get overly focused on geeking out with the toys that they forget about the …
What Is Holding Your Angular Team’s Productivity Back? Read More »
It is no wonder, that the highest performing companies in the IT industry are also the ones who push the most delivery responsibility on the engineers as a contrast to the classical chain of handovers for ensuring “segregation of duties”. There is an inverse proportional relationship between how much segregation of duties a company enforces and their …
How to Implement Continuous Delivery in Highly Regulated Companies Read More »
I see many teams believing that npm packages are the way they should share code in Angular projects. The problem with this is that this creates a lot of friction for code sharing because: Every shared lib needs to have its own CI/CD pipeline Each CI/CD pipeline should handle versioning of changes Every time a …
Why Angular Teams Fail at Code Sharing and How This Monorepo Approach Will Fix It Read More »
Handling anything at a big scale always is very different from when things are small. The differences can be in the number of people working with something, the business impact of decisions and the ability to enforce the execution of decisions at a large scale. I have in the previous post talked about different tools …
Angular Automation: 6 Things That Should Be Automated in Enterprises Read More »
It seems that a lot of developer teams fall in one of these two categories for end-to-end testing: Have no end-to-end tests because they are too hard to create Have too many end-to-end tests, making many fulltime jobs to maintain Either one of these is not practical as the first one is causing the team …
End-To-End Testing with Protractor: A Pragmatic Guide to Get Started in Your Team Read More »