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 …
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 »
The good thing about crisis situations is that they force you to think out of the box. If you have read my post about implementing continuous delivery, you know that I recommend the use of feature environments; an environment containing only a specific feature branch to QA a feature before it gets released. Let me tell a …
Feature Environments in All Environments – A Guide to Faster Delivery Read More »
These days everywhere I go people seem to talk about wanting to deploy to production more often. It seemed like an endless battle trying to deploy more often as the amount of code to deploy seemed to bulk up in big batches, while we were rambling about buzzwords such as “CI/CD” and “feature toggles“ without …
Implementing Continuous Delivery through Five Steps Read More »