Skip to content

Instantly share code, notes, and snippets.

@joel-oe-lacey
Created March 30, 2020 16:31
Show Gist options
  • Save joel-oe-lacey/5696118c35363b363f26d43aa3a487d7 to your computer and use it in GitHub Desktop.
Save joel-oe-lacey/5696118c35363b363f26d43aa3a487d7 to your computer and use it in GitHub Desktop.
Dev.To Machine Collection Retro - Joel, Ali, Phil

Machine Collections - Joel, Ali, Phil What went well?

  • We passed! This project had some struggles both with the climate and just trying to contend with the cross-pol even with the extension.
  • Managed to connect and sync up well as a group.
  • Did great at staying on timelines & communicating effectively, held a stand-up each day. Good buy in from all team members.
  • Came out with a good retrospective of how you would approach a similar code base, how you'd work with a cross-over team. In general helped enhance comfort levels with a similar workflow on a potential job.
  • Got a chance at learning and exploration without going overboard.

What could be improved?

  • Maybe some more cross-over learning.
  • Everything could be improved over a longer time span: more personal communication, knowing our own limitations of technical knowledge.
  • Knowing when to take personal time when needed, being self-aware of burnout.
  • Took a while to get into a flow and find the rhythm.

What are we taking into our next/project job?

  • Actively looking for roles that offer mentorship and learning opportunities. Allows us to learn more via asking targeted questions.
  • Strong PR workflow really helped with communication.
  • Openness and willingness to learn from code and other people working on similar paths.
  • Navigating a big codebase.

Final Takeaways

  • Thanks to all team members for their openness, positivity and contributions!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment