12 posts about CS3216


Angular 2 is terrible

We used Angular 2 for our frontend. I was not involved in this decision, and I came to work on the frontend relatively late in the project. This post is not meant to be a comprehensive review of the framework, but rather a collection of observations after using it for a little more than two weeks. I don’t claim that using it for two weeks makes me an expert, and welcome any corrections, but for what it’s worth, I consider using Angular 2 one of the biggest mistakes for our project.

Continue Reading

On the Proper Care and Feeding of REST APIs - Part I

After working the full-stack for assignment 1, and purely on the frontend for assignment 3, for the final project I get the exciting task of designing and building a backend API from scratch to power the two frontends of our final project product. I’ve only ever constructed APIs twice before, and both times with toy projects that had at most one or two endpoints. This on the other hand is significantly bigger - for the first week of the project, by GitHub’s estimation, our project repository had more API documentation than code!

Continue Reading

Assignment 1 and 3 Post Mortem

These are the highlights of things I’ve learnt from the last seven weeks of CS3216. I have meant to do a post-mortem after assignment 1, but Assignment 3 and school got in the way, so instead here’s a 2-in-1 deal - a post mortem of both assignments 1 and 3.

Continue Reading

Slack: The Seminar: The Review

This is a critique of Slack, as well as a critique of a critique of Slack. Slack is a the popular instant messaging and team communications software launched in 2013 and quickly grown to prominence as one of the fastest growing startup, boasting one million users and a valuation of over a billion US dollars in less than two years since its launch.

Continue Reading

Software engineering team project quickstart

One of the things I learnt during group formation is that getting all the information needed from a group of strangers is a bit of a pain. Slowly collecting information over instant messaging is cumbersome and annoying. A contact sheet shared between everyone is the way to go here. I’ve created one here that’s useful as a template for future software engineering teams.

Continue Reading