# Stop, Go, Continue (Week 1) ## STOP :hand: - going off topic toooooo much. Still a bit, but not loads lol. - going down rabbit holes (with code) ## GO :point_right: - Start using primitives more freely - using BEM naming conventions from the start - initialise readme from the beginning and take equal turns adding to it. Make a habit of checking readme before lunch and adding to it. - every hour have a group catch up where: - discuss changes we have made, and update if needed (namings) - all git push/PR/pull/merge - discuss if still need more time as a pair or ready to swap and work on a new issue - discuss if stuck on any code ect , design issues ## CONTINUE :roller_coaster: - focusing on the MVP - catching ourselves before we go down rabbit holes (with code) - being spoons :spoon::spoon: - being proud of our work, cause we defo should! - churning out the quality content, both technical and social - hablar en español - being ¡LOUD! - keep communicating with other team members before/when pushing to github/ letting others know there are PR / git pulls outstanding --- ## Notes - have a 'code' word for catching ourselves before we go off topic i.e. 'waffle' - naming conventions: ensure they are all readable early on - swapping groups every hour or so with regular reviews and set times / reconvening every hour and discuss swapping groups and assessing git pull requests/merge etc. - Our team dynamic worked really well - Make time for pair programming and pair someone who is stronger in one area up with another who isn't so strong in that area or wants to learn more