Our learning: Sprint Two - acodeguy/acebook-rails-gang-of-four GitHub Wiki

  • Working with Rails and Devise is teaching us to work with a convention over configuration toolset, IE where we just have to make sure the way we are coding, organising our file structure, and naming files, classes etc. follows a certain convention. It has also presented a new learning challenge, which is finding out what the toolset is doing for us and what we have to code. To research this, we've used a combination of googling and testing the framework - using print statements to find out what it is doing for example.

  • Ideally next time we'd set up Heroku using either a team github account (with our repo) or the person who creates the repo is comfortable with having their credit card details on Heroku (as that is needed to create a team in Heroku). This would enable all team members to access and configure Heroku.

  • Good learning that almost always an existing library / component we can reuse to do anything boilerplate.

  • Limitations of Travis and free services in general. Travis builds are very slow.

  • Bit of delay in pushing to master, didn't plan releases, but hasn't taken too long.

  • Perhaps didn't respond quickly enough to the lack of work - could have asked for more, sooner.

  • Would be good to have a short checklist for things to cover in retros and standups.

  • Need some reflection time as a team to recap our git process to cement understanding of it.