I’ve reached the conclusion that Angular is hard. It will take some getting used to with running through several exercises before I feel comfortable enough with it.
Today we worked with Angular alongside Rails. It was cool seeing how we can create our own APIs when we need to be able to work with updating the API data. It was weird seeing how Rails as the back-end fits together with Angular as the front-end. We walked through putting together a couple of single-paged applications with the Rails/Angular combo, and I noticed that the Angular server acts a little wonky at times when working on updates.
In the afternoon we walked through working on a SPA with Firebase. Firebase is a Platform as a Service (PaaS), that offers a number of cloud-based computing services, including a realtime database. Firebase uses Websockets to maintain a constant, open connection between the client and the database. We used AngularFire, which is a way to connect an Angular application to a Firebase DB.
I had a chance to sit-in on a Scrum meeting at National Geographic, which was a pretty insightful experience. As someone who is coming from a background in working for nonprofits, it was great to get to see the planning phase that other companies go through.
Afterwards, we worked with Angular once more, although this time we combined our knowledge of Angular with API calls, putting together our first Angular CRUD application. It’s going to take a little while to get used to the format for Angular applications, with controllers and views, but I’m determined to ‘get it.’
I learned about how directives are markers on a DOM element that tell Angular JS’s HTML compiler to attach a specified behavior to that DOM element. Angular expressions remind me a lot of inline Ruby code, which allow you to execute JS code in HTML files.
We got a head start on our homework, where I found myself running into errors. Hopefully when I work on it some more this weekend, all will get better.