Migrating Legacy Web Applications to AngularJS
Video: Migrating Legacy Web Applications to AngularJS
If you want to see the entire presentation, click on the updated slides below.
What is a legacy application?
A legacy application could be an application that’s been cobbled together over the years. Perhaps with a bunch of features slapped onto it without much intentional thought as to what it might end up like. As a result, over time it just becomes a mess that might need to be scrapped.
Or it could be a really powerful application that’s been in development for years and years but it’s become convoluted and extremely hard to maintain. Another issue is that there are likely only a few people who even know how to keep it up and running.
Why is a legacy application like this a problem?
- It ends up costing more to maintain
- It’s likely slower to release to production
- It produces low moral on the team
So what’s the answer? A new technology perhaps? Sadly, no. As we explain in the video, new tech by itself won’t give you costs savings, faster time to production, or a happy team. So what will give us these things? Cleaner Code!
But before we can talk about writing Cleaner code, we need to talk about the team that’s going to be writing it.
How do you set a common baseline on your project? By using Coding Standards!
Once you and your team have worked out the Coding Standards that are right for you, be sure to hold each other accountable to the rules you’ve set.
In this video, we walk through how my team handled accountability once we set up our Coding Standards as well as how we used data binding, services, dependency injection, and components in our AngularJS app to write Cleaner Code.