Greenfield projects are over! We managed to code out a large amount of iHammer over the solo week. It certainly wasn't complete but I thought the team got a lot done and the end product was respectable.
Now we are onto legacy projects, where we choose another team's project to work on for the rest of the week.
We ended up going with tikr, a social network for developers that meshes together LinkedIn and GitHub.
Why We Liked It
- There are a lot of data visualization and search possibilities with LinkedIn and GitHub info. Tikr's pie-chart of frequently used languages on a users' GitHub profile was the most eye-catching part of the project:
- Their stack is very similar to ours--except MongoDB instead of MySQL. Just a little extra D3 and C3 for data visualizations.
- Similar file structure--the original team had also used Yeoman to generate their basic scaffolding.
- Decent code (so far as I can tell...)
Why I Dislike It
- No documentation. At all.
- Ugh, not another social network.
On the work-flow front, the team decided to ease back on the iron-fisted documentating, testing and waffle.io-ing we had for our greenfield project. We are not scrapping it all together--we put together some basic stories, stuck a dozen or so issues on waffle and are using Circle for testing. But this time, we are going to put all of our energy into the actual project.
With the Greenfield project, I got some proper exposure to Express.js. For this project, I want to focus on things that I have absolutely no idea on: authentication/third party APIs and deployment. I am also going to attempt to create a whole new user-type (fullstack) and dabble a little with the user profiles (front-end).
For deployment, the team agreed to deploy on AWS, which I'm looking forward to learning about but I will also be deploying to heroku by myself just to try it out.
We have until Friday (or Saturday?) to finish up so I'm looking forward to seeing what our interpretation of Tikr ends up like.