For this blog post I chose to focus on something I have used multiple times but still did not fully understand, this being Angular. I have been using it only on my own personal project to build a web application, but have not actually sat down and researched what I was using. Thus for this blog post I will explore exactly what Angular is, and specify some situations where it could be useful to implement. To begin, I will try to define exactly what Angular is.
Since, as stated, I do not have much knowledge about exactly what angular is, I found some other posts to reference. The first of which is Angular Introduction, written by an experienced programmer Ilya Bodrov-Krukowski. I would highly recommend checking out this blog post, as it goes far more in depth than I will be able to. From my relatively brief time with Angular, I assumed it was just a web application development and hosting platform, but the answer is not this simple. This initial assumption was not entirely wrong, just missing some parts. As stated in Angular Introduction, Angular is really more like a collection of tools that can be used to develop a web application and it defines how the app should be designed and organized. Essentially, Angular sort of guides you on exactly how to go about making the app, which would explain why I had a relatively easy time working with it. Some other important features Angular provides is data binding and dependency injection, both mentioned in Ilya Bodrov-Kurkowski’s blog post. Data binding essentially meant that you could see changed data in a view in real time and dependency injection, “allowed application components to be wired together in a way that facilitated reusable and testable code”(Angular Introduction). These are extremely useful, as databases are used on a variety of applications, and being able to reuse code is always helpful. But why should you use Angular?