We are not a free boot camp responsible for teaching you skills, but we do provide an opportunity for you to practice what you learn and build a portfolio. What you get out of the experience depends on the effort and time you put in.

Best Practices:

• Document document document. Documentation is how you build a lasting legacy on a project, and also how you build something you can put on your resume or on LinkedIN.
• Take Notes and Record Calls. More people will be joining asynchronously, so consider designating a note taker and/or recording calls
• Over-communicate. Ask more questions, drop notes on slack, create more github issues or to-dos, it’s easy to miss details when we’re not face-to-face.
• Assume the best intent. Communication details can get lost when we’re all remote. It’s usually safe to assume that someone might be busy, distracted, etc. rather than rude or uncommunicative

Expectations

• We find that, to find the success you’re looking for, you’ll need to spend at least 3-5 hours per week on projects.
• The length of the contribution is up to you, and many members stay with us for years, but we expect project contributors to stay for at least 3 months.
• If you're not able to make that commitment, we're happy to have you at our events, and would love to have you join a project when your time allows. If you can't contribute at this time, or if circumstances change, we appreciate you communicating that. Don't ghost your teammates 🙂.
• Going on vacation? Have plans next Wednesday? Just like the professional world, set expectations, let your team know what you’ll do and when. We all need time off!