As an Angular consultant, the main problem I see new Angular developers have is how to use RxJS efficiently in Angular apps. In other words, how to use it to create a scalable and maintainable reactive architecture. What I see instead is an abuse of RxJS, which is a completely natural thing to do, when you don’t know how to use it efficiently. This blog post will shed some light on this and will show you why and how to refactor your Angular apps to use a reactive architecture.

The problem with imperative programming

By definition, imperative programming means to use statements to change a systems state. In this way of programming, you will be setting data properties and maintaining the state explicitly through commands. The problem with this, might not be obvious once the app is small but might be the biggest root of Angular bugs as the app grows.

Read more here.