Week Eighteen
Posted on January 8, 2018
(Last modified on February 28, 2018)
| ovieh.com
This week we added another tool to our toolbox, MongoDB. And unlike MySQL, it does not care what you put in to it. It just accepts the data. Which is a blessing and a curse. To remedy this, there exists a project called Mongoose. Mongoose provides a MondoDB database with an ORM, which allows for validation. Since we previously learned Firebase, it was relatively easy to pick up Mongo. We just had to learn how to implement it with Node.
[Read More]Weeks Sixteen & Seventeen
Posted on December 20, 2017
(Last modified on February 28, 2018)
| ovieh.com
It has been a challenging last couple of weeks. We concurrently covered testing, both unit and functional, and completed our second group project. One of the toughest aspects of our group project is simply coming up with an idea for an application. We kicked around a few ideas, but eventually led drawing game, kind of like Pictionary, where one player has a clue and other player must guess what the drawer is, drawing.
[Read More]Week Fifthteen
Posted on December 3, 2017
(Last modified on February 28, 2018)
| ovieh.com
This was a short week in terms of new material, as it was running concurrently with the planning of our second group project. We build off the knowledge we gained last week in building our own ORM, and used an off the shelf model, Sequelize. I found Sequelize itself to be pretty easy to use, since it is promise based. Dealing with callbacks can get messy. Our project this week was merely to refactor last week’s project, were we created are own ORM, using Sequelize.
[Read More]Week Fourteen
Posted on November 26, 2017
(Last modified on February 28, 2018)
| ovieh.com
This week we dove deeper into Express and covered Handlebars.js, a html templating engine. HTML templating provides a bridge between our JavaScript and our content, allowing us to decouple our HTML structure of the data within. Handlebars provides pretty easy to understand syntax and even allows block expression. As an example, let say I had list of burgers I want to iterate through and add each burger as a list item, it would look like this:
[Read More]Week Thirteen
Posted on November 20, 2017
(Last modified on February 28, 2018)
| ovieh.com
We are starting to put it all together. Our project this week was to create a friend recommendation app not dissimilar from Tinder. It is almost a full-stack app, it doesn’t quite have data persistence through a database. Class is starting to get complicated, but when you step back and think about things, the concepts make more sense. When you are running a web server, it makes perfect sense that your server won’t serve something it has no idea about, such as static files, unless you explicitly do so.
[Read More]Week Twelve
Posted on November 11, 2017
(Last modified on February 28, 2018)
| ovieh.com
This last week I became reaquainted with MySQL. It’s not so bad. The syntax is relatively straightforward. The keywords are close to to natural language. This was another week getting familiar with the power of Node.js. It is really easy to integrate some really powerful tools.
Our assignment this week was to create backend for store using MySQL running on Node.js.Working with MySQL was pretty straightforward, updating, selecting from, and inserting into the database.
[Read More]Week Eleven
Posted on November 1, 2017
(Last modified on February 28, 2018)
| ovieh.com
This week was surprisingly challenging. What makes this program interesting is that we often are giving just enough tools to complete assignment. The examples we covered in class were not as complex as the assignment turned out to be. Albeit, it could be me overcomplicating things. I tried to abstract this project as completely as possible. I also tried to cover every edge case, every error.
This weeks project was a bit of remix.
[Read More]Week Ten
Posted on October 23, 2017
(Last modified on February 28, 2018)
| ovieh.com
This has been my favorite week of learning yet. This was our introduction to Node.js, which is a JavaScript runtime engine. What that all means is that it allow us to use JavaScript outside of the browser. That opens up doors. Prior to Node.js developers had to learn a second language for the backend, such as PHP or Java. Now, no need. With just one language a developer can handle the tasks of both the front and backend of the stack.
[Read More]