Team

Contact info:

  1. Grayson Clark, Backend Engineer: graysonjclark12@gmail.com / gclark@unc.edu/ graysonj@ad.unc.edu / (828) 729-0328
  2. Jason Manning, Documentation Manager + Code Reviewer: jason.manning.01@gmail.com / jasonman@live.unc.edu / (984) 528-6813 
  3. Matthew Reddy, Project Manager + Code Reviewer: mjreddy@unc.edu / matthewreddy12@gmail.com / (704) 692-5499
  4. Connor Morin, Frontend Engineer: cjconnor@email.unc.edu / cmorin92702@gmail.com / (336) 596-9888
Contact Us!

Rules and Expectations

  1. Team Behavior
    • Communicate early and often, especially in regards to potential tardiness or absence from team meetings, class, etc,
      • Ideally, text multiple hours before, if possible (emergencies happen)
      • If you miss something, text the group an explanation when possible and plan to catch up on work
  2. Coding Practices
    • Keeping track of branches on git will be difficult, so to make absolute sure, any time you push to the repo, please text the group beforehand and let them know to make sure everything is alright
      • If unsure, can always just create a new branch
    • Comment code!
      • The code we were given was not provided with much documentation, so it is our job to document it as well as we can
      • Add docstrings at the beginning of every file explaining what the file does
      • Add docstrings for various functions as well
      • Note any code that is being used for testing purposes
    • As for style, generally try to follow the “PEP 8 – Style Guide for Python Code”
      • If you are converting a line of code and/or notice that it does not adhere to the standards, please try to fix it
    • Generally just make sure things are done neatly and are clear for both group members now but also anyone else that may be working on this in the future, as it is something that would have helped us greatly

Schedule

  • Coach meetings every Friday at 12:30 on Zoom
  • Client update email every 2 weeks
    • Meetings scheduled as needed, usually on Zoom
  • Team meetings after every Tues/Thurs class at 3:15 (may be cancelled or moved to Zoom if a meeting is not necessary for a given week)
  • For specific meeting dates/logs and what was discussed at meetings, see the “Journals” tab

Individual Information

  1. Jason Manning:
    1. Response time: A few hours
      1. Will make people aware if OOT / OOO, in which case response will be slower
    2. Best way to reach me: Texts / call if urgent
    3. Assume i haven’t seen it/ am busy, feel free to double text I don’t mind
  2. Matthew
    1. Should respond pretty quick usually. Can reach out any way, text works great. Generally will respond fairly quickly if a response is needed; if not, probably haven’t seen it yet
  3. Connor
    1. Response time: usually a few hours at most, but as soon as I see it if not busy
    2. Best way to reach: text (also can call if urgent)
    3. No response: means I am busy (class or other), try to respond as soon as I see
      1. Pretty much the same as Jason’s
  4. Grayson
    1. I can normally be reached from 8am-10pm, will try to respond as quickly as possible
    2. Best way to reach – Text
    3. No response: Sleeping/Busy, feel free to double text if urgent