...
Welcome to Northeastern Electric Racing’s Software Solutions team! We are excited to have you join!
Firmware Onboarding
FinishLine Onboarding
What Now?
Learn about the technologies we use and join Slack (see below)! If you are not familiar with the technologies, don’t worry! We have some learning resources to help with the basics! You may also follow tutorials found in the NER curriculum for this information as well as attend the Learning Sessions. When you are ready to start development on the codebase, please read through the contributor guide on the GitHub repo.
Join the Slack!
At NER, we utilize Slack for communication. We ask that you download Slack on both your phone and computer to be able to reliably view and respond to any communication. Here is a quick start guide for Slack (on desktop). Most of the information in this should translate over to mobile. Please note that notifications may be off by default, so please ensure that they are turned on. After this, go through the channels that exist in the Slack and join any relevant channels (#software, #software_env-setup, and #software_pr-review for starters). Additionally, try to avoid DMing people (unless it’s a personal issue). Keeping communications public is better because someone probably will have the same question as you and it keeps everyone up to date. It also allows more than one person to help you.
Organization & Leads
Now who should you ask for issues?
Our Product Team exists as a wonderful resource for all developers on the Software Solutions team. Product Analysts, Product Managers, and our Head hold key business facing information for all parts of our application, and are a great resource to go to if you have non-technical questions. Make sure to reach out to relevant analysts, PMs, or even Peyton first before reaching out to others for these questions in case they can answer your questions.
For technical or coding questions, try to contact anyone you are pair programming with or working with on a feature. If this does not help, move to the tech leads & senior developers. Next step is to check in with a Head, Sean Walker for FinishLine and Dylan Donahue for Firmware. If they cannot answer anything, please contact the Chief Software Engineer, Peyton McKee