Byte4, Acebook, Day4 = Fun

Irfan Durrani
acebook-byte4
Published in
2 min readApr 12, 2018

Here at Makers, we are working on our first ever 2 week project. It’s called Acebook (not to be confused with some in-trouble social media platform). Although with some similarity, our one is obviously better, just trust us on this. I mean at the very least, we won’t be appearing in front of the Congress explaining ourselves (or at least that’s the plan anyway).

Definitely not us

So today was our day four of working on this week project. As soon I walked in, I was welcomed by Antonio and Agnes. Although half asleep, I could still sense them itching to get into coding and start to give the project some shape, to write some code, some tests, fail them pass them, get into that Red, Green Refactor cycle. And who can blame them after 3 days long research marathon to understand Ruby on Rails.

Rails, oh yes, Rails. It’s like your favourite butler. You tell Rails what you want and it obliges. Sometimes giving you more than you asked for. If there was ever a competition between Alfred and Rails, I’d put my money on Rails. Partly because Alfred isn’t real but you get the gist.

Rails: Like Alfred but better.

Anyway, today we started to give our project some shape. We worked in pairs for the first time in the week. Antonio and Agnes worked on feature testing the user authentication and Ammar and I dived into the world of posts and likes. We didn’t tell Agnes and Antonio but we plan to add dislike feature, you know you want that. We also sneaked in some bootstrap because why not?

Here I have to give shout out to Trello. It’s just fantastic and a great help when setting up team goals and keeping track of them.

One thing we got stuck on was displaying actual time, Our postgres database was not saving the date properly and that was giving a massive headache when testing with Time.now but as they say, when you have Ammar and google, you get the work done no problem.

Tomorrow’s target? Full sail ahead. Make it happen and just bloody code! (and test of course).

That’s us tomorrow.

--

--