Resilient Coders

Show respect by embodying positivity and offering people the benefit of doubt. Take initiative in giving and acting without waiting to be prompted. Foster an outlook that highlights the strengths of individuals. Embrace the richness of diversity, encompassing various backgrounds, perspectives, and the elements within and beyond our control. Hold yourself responsible for your actions. Approach every task purposefully and acknowledge that both your own mistakes and those of others are integral to growth. Demonstrate diligence by dedicating your utmost effort, not only to enjoyable tasks but also to those that challenge you.

As a Resilient Coders community member, you are responsible for being aware of these Community Guidelines and abiding by these rules, both virtual and during in-person events that are hosted and / or associated with Resilient Coders. It is expected that you will uphold our community values and interact in a manner that promotes a safe, respectful, and collaborative environment. Resilient Coders community members include but are not limited to Resilient Coders staff, board members, prospective students, enrolled students, alumni, mentors, hiring partners, volunteers, contractors, etc. These Community Guidelines have been developed with the assistance of the staff, alumni, and enrolled students, and will continue to evolve as we proactively seek feedback from the Resilient Coders community.

We ask community members to share their pronouns. We honor and respect one another for how we show up in the world. We do not make assumptions about gender based on photos or names used on virtual profiles.

We encourage discussion of sensitive and difficult topics so that we can support each other, help each other find solutions, and problem solve together. Lean into discomfort. Due to the sensitive nature of many of these discussions, please keep what is said in these spaces - whether virtual or in person - confidential unless you receive permission otherwise. Be especially cognizant to avoid sharing identifying information, and remember that anything you do share on Slack is seen by thousands of people. Always ask the original poster or speaker if they would feel comfortable having their post or experience shared.

Each of our members play a role in establishing and promoting a welcoming, positive, inclusive, and encouraging community. Discussions, posts, actions, or comments that promote hatred of any kind - including, but not limited to, racism, sexism, transphobia, homophobia, biphobia, queerphobia, ableism, and ageism - are not acceptable in Resilient Coders spaces and will not be tolerated. Such actions may result in you being removed from virtual or in-person communities.

Trust that everyone in this group has each other's best interests at heart; but if someone says something incorrect or hurtful, name what impact that has. Just because you haven’t experienced something yourself, doesn’t mean that experience isn’t valid. Don’t dismiss another’s ideas before asking for clarification.

Speak up and have your voice heard, but also be cognizant of how much space you're occupying and take a step back when needed. Encourage folks who may not usually speak. Let people of different backgrounds tell their stories and experiences. Listen with intention. Listen to understand. We have a lot to learn from each other!

Many members of the community spend their precious and valuable time sharing guidance, advice, introductions, etc. If someone does this for you, acknowledge their comments, take time to say thank you, and pay it forward when you can.

Resilient Coders is a harassment-free community for everyone, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, visa status, age or religion. We do not tolerate harassment of any community members including but not limited to Resilient Coders community members include but are not limited to Resilient Coders staff, board members, prospective students, enrolled students, alumni, mentors, hiring partners, volunteers and contractors. Any individual violating these community guidelines will be expelled from the Resilient Coders community at the discretion of the Resilient Coders staff and/or Ethics Committee.

Violative behaviors include but are not limited to:

Creating noise or other disturbances that disrupt Resilient Coders activities, or that disrupt community members.

Slurs, Name calling, and derogatory terms
Targeted or Excessive Profanity*
Offensive comments or patronizing language that reinforce social structures of domination related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance, body size, age, race, religion, and/or visa status
Unwelcome comments regarding a person’s choices and practices, including those related to food, health, parenting, drugs, reproductive choice, and employment
Deliberate misgendering or use of ‘dead’ or rejected names after a pronoun preference is communicated
The general or casual use of non-targeted profanity in conversation is not a violative behavior. Resilient Coders community members should respect those who express discomfort with use of such language

Publication of non-harassing private communication
Attempting to suppress or exclude the participation of someone in a community forum
Doxxing individuals, releasing their personal information or images without explicit permission online
Media that has been technically manipulated, photoshopped or doctored in a way that poses a risk to the safety or reputation of others or Resilient Coders
The redistribution of others’ intellectual property without their consent, whether in another Resilient Coders forum or external use
The redistribution of a community member’s external private social media content in a Resilient Coders forum without their explicit consent
Plagiarism: Resilient Coders defines plagiarism as using as one’s own, the words, ideas, data, code, or other original academic material of another without providing proper citation or attribution. Plagiarism can apply to any assignment, either final or drafted copies, and it can occur either accidentally or deliberately. Claiming that one has “forgotten” to document ideas or material taken from another source does not exempt one from plagiarizing
Unauthorized Collaboration: Resilient Coders defines unauthorized collaboration as instances when students submit individual work that is substantially similar to one another. While several students may have the same source material, any code, analysis, interpretation, or reporting required by an assignment must be each individual’s independent work unless Resilient Coders has explicitly granted permission for group work
Using a name or likeness that is not your own
Impersonating a brand or person
Misrepresenting your affiliation with a group, organization, or entity
Misrepresenting your position in Resilient Coders externally or to other members of the Resilient Coders community
Making verbal or written statements on behalf of Resilient Coders Leadership

Members may reference Resilient Coders when creating events, informal forums, or gatherings for the Resilient Coders community virtual or in-person but are obligated to make clear to participants that it is community-led and not an official experience organized by Resilient Coders leadership. Organizers of such informal but branded experiences are expected to uphold and enforce our Code of Conduct.

Harassing photography or recording, including logging virtual activity for harassment purposes
Sustained disruption and criticism of discussion, talks or other events, meant to provoke, offend, or divide
Inappropriate physical contact
When in-person, physical contact and simulated physical contact (eg, textual descriptions like “*hug*” or “*backrub*”) without consent or after a request to stop
Threats of violence
Bullying, social exclusion or isolation, humiliation or degradation, embarrassment, or causing emotional, psychological, or physical harm to a community member
Incitement of violence towards any individual, including encouraging a person to commit suicide or to engage in self-harm
Deliberate “outing” of any aspect of a person’s identity without their consent except as necessary to protect vulnerable people from intentional abuse

Engaging in lewdness or indecency
Sharing sexual images, links, or any other form of medium or behavior
Deliberate intimidation, stalking, or following
Unwelcome sexual attention
Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others
Continued one-on-one communication after requests to cease
Bribery

Possession or consumption of alcoholic beverages by persons under 21 years at Resilient Coders events or events associated with Resilient Coders
Furnishing alcoholic beverages to any member under the age of 21 years
Excessive consumption of alcohol is prohibited regardless of age. Being under the influence of and/or the abuse of drugs is prohibited
Behavioral symptoms frequently associated with excessive consumption or intoxication may include, but are not limited to, impaired motor-skill coordination, difficulty communicating, vomiting, glazed/red eyes, the smell of alcohol on one’s breath, verbal and/or physical aggressiveness, destructive and/or disruptive behavior, and engaging in any behavior that may endanger oneself or others
Resilient Coders are not permitted to consume, be under the influence of, possess, manufacture, distribute, or sell illicit drugs during any Resilient Coders activity. Reasonable suspicion of possession or use of illicit drugs and substances in person or virtually may subject the person involved to an investigation and/or disciplinary action

Resilient Coders community members should not advocate nor encourage any of the above behavior, and cannot implicate the organization or its members in the violation of the law.

We are only as strong and supportive as our community members allow. Your help is critical in making Resilient Coders a safe and inclusive community.

While the staff has access to all slack channels and some are moderated on a regular basis by staff and volunteer community members, we believe in community spaces being safe from surveillance and in our members’ right to privacy. We cannot see and read every exchange that happens on the platform. If you see anything that you believe breaks our community guidelines, please reach out to a staff member with screenshots of the post and/or a link to the post or comments.

Conduct at non-Resilient Coders activities is viewed as the members’ personal business.

We take every report seriously, and if someone is found to have broken the Resilient Coders Code of Conduct, there will be an internal investigation that may result in a verbal or written warning, expulsion from the community, and/or immediate termination. These measures may involve removing the offender from the program immediately and without warning. We will also prioritize working with those affected to determine what the next steps should be.

All community members, including staff, volunteers, and mentors must comply with the guidelines and are not exempt from an internal investigation, verbal or written warning, and expulsion from the community and/or termination.

Staff and event organizers have the authority to address any actions that are intentionally disruptive to the program or create an unwelcoming environment for participants. This pertains to actions with the explicit intention or noticeable effect of causing disturbance or hostility, as well as missing or attacking reasonable requests for behavior changes.

These guidelines are applicable to all Resilient Coders events and spaces, whether in person or virtual. These guidelines extend to all RC-related social activities. If you see something that you think violates these guidelines, please contact a staff member with screenshots of the post and/or a link to the post or comments.

If someone in the community makes you or anyone else feel unsafe or unwelcome, please report it as soon as possible. Harassment and other code of conduct violations reduce the value of our community for everyone. We want you to feel welcome and happy. People like you make our community a better place.

You may submit your complaint anonymously and/or personally.

You can make an anonymous report here.

We can't follow up an anonymous report with you directly, but we will fully investigate the complaint and take the necessary action to prevent a recurrence.

When taking a personal report, our staff will ensure your privacy and that you cannot be overheard. They may involve other staff to ensure your report is managed properly, and will ask for your permission before sharing. Once safe, we'll ask you to tell us about what happened. This can be upsetting, but we'll handle it as respectfully as possible, and you can bring someone to support you. You won't be asked to confront anyone and we won't tell anyone who you are.

Our team will be happy to help you figure out the best way to support you or next steps. From contacting venue security, local law enforcement, local support services, providing escorts, or otherwise assisting to ensure your safety.

You can make a personal report by contacting a key staff member.

Boston police department non-emergency: 617-343-4240
Boston medical center: 617-638-8000
Boston sexual assault hotline: 1-877-785-2020
Boston Local taxi: 617-536-5010

Philly police department non-emergency: 311
Philly sexual assault hotline (WOAR): 215-985-3333
Philly Local taxi: 215-535-6700

Resilient Coders may host in-person events at different venues or we may be invited to attend other tech events. Many of these spaces have cameras for security purposes, and you are expected to represent yourself and Resilient Coders in the best light possible. We cannot afford to lose partnerships or access to a space due to reckless behavior.

Respect an individual’s personal space, whether you know them or not. Always ask for permission before touching someone, taking their photo, or filming them.
Leave event spaces better than you found it
Be mindful of your volume in co-working event spaces, where there are other businesses around
Do not disrupt other companies' space or common areas
There are lots of businesses that use co-working spaces, do not touch or take items, this is theft
Do not take items from personal fridges
Do not use conference rooms/phone booth for calls unless given permission
Be considerate when enjoying the free snacks. This is not a grocery store.
No sleeping on the premises
Any violative behaviors listed in the Safe Space Policy (see above)

By Joining our slack team you agree to abide by Resilient Coders’ Core Values, Code Of Conduct, Honor Code, and Safe Space Policy. We created this Slack community as a way for you to connect with each other in meaningful ways. We ask that you do not share any other links to external meeting spaces, please only use slack for your communication purposes. To get started on slack, take a look at our Slack Onboarding guide here.

If you think your question or comment is relevant to the community-at-large, put it in a public channel. If it’s specific to a person or a handful of people, keep it private. Give as much context as possible for your question or comment. Share what you know and only give feedback when solicited.

This Slack community is for:

Getting to know each other
Sharing knowledge
Inspiring and helping each other out
Thinking through challenges together

This Slack community is not for:

Share solicitations or self-promotion that doesn’t add value to the community-at-large
Spam people through private messaging
Troll fellow community members
Upload objectionable or inappropriate content
Pursue romantic relationships, and/or make sexual advances, whether "warranted" or "unwarranted."
And any violative behaviors listed in the Safe Space Policy (see above)

Resilient Coders encourages enrolled students to ask for help and communicate publicly. Thinking about our in-person roots, there was a lot of value in being able to see what other students were asking and learning, even if passively. It also minimizes mentors having to answer the same questions multiple times. Finally, it adds a layer of job readiness: communicating and finding answers via Slack channels.

Students can @/program-team and @/staff in their respective bootcamp channel for questions and any available staff member can answer. Staff hopes that we can clear up any miscommunications and get to questions quicker. Students can still DM in case of an emergency or to set up a 1:1 meeting to address sensitive conversations.

For Community members who are actively engaged with enrolled students:

If you're working with a student, we ask that you try creating a thread in the #_help channel to communicate with them and share code snippets. You can preface it with "1:1" to let other mentors know they may not need to respond if you'd like, but the thread will be available for other students to see.
Aside from setting up meeting times, please encourage students / feel empowered to move the conversation into the #_help channel.

We believe our work is more effective when we learn and collaborate with each other. Recognizing privilege is important to creating a safe and welcoming environment. We ask that all community members reflect on their social positions re: class, language, body, legal status, etc., and be a supportive community member to people more marginalized than yourself. Resilient Coders is actively reframing knowledge and actively changing power dynamics. Please engage these practices:

Listen and learn, even when you feel confused or uncomfortable.
Educate yourself instead of asking others to educate you. Please see a list of educational resources below and check out Mailchimp's guide on Writing About People.
Don’t take credit for ideas originated by people on the front lines.
Be an ally when no one is watching.
Acknowledge your privilege.
Contribute resources: Time. Money. Visibility. Opportunity.

Community Guidelines

COMMUNITY GUIDELINES PLEDGE

Bootcamp

About

get involved