| Table of Contents |
|---|
| Info |
|---|
This tutorial assumes you know absolutely nothing about software development, Git, or coding. If anything is unclear, feel free to reach out for help !on the |
By the end of this list, you should be in a place where you are more than ready to start work on the car. A lot of this stuff you might have already done or don't need to do if you've dabbled in software development before, but if you're fresh out of cornerstone you might need to go step by step. Go through at your own discretion, but each step is pretty important.
General Onboarding
Make sure to look over this landing page and dive into Confluence
You might want to use this glossary to reference while trying to understand things
Development Environment Setup
Follow this guide to setup your development environment.
Git
NER uses GitHub and Git to manage software development
Development Environment Setup
Follow this guide to setup your development environment.
Coding Standards
Hardware We Use For Product
Note that for NER, we are using Embedded Linux for processing Telemetry Data and wireless communications, and all of the real-time processing happens onboard microcontrollers. These microcontrollers are literally just chips on our custom PCBs, not just Arduino development boards you may be used to.
Other Tools We Use For Development
Customize as you like, all of our tools are in Docker containers or venvs as of now
| Expand | ||
|---|---|---|
| ||
Coding Basics & Helpful Tips
If you're interested in learning Python and coding higher-level applications, try to walk through this tutorial. If you do all the exercises you'll get a pretty good understanding of Python. If you're interested in learning C++ and lower-level embedded code, try to walk through this tutorial. This should lay the groundwork for coding with objects, constructors, pointers, etc, especially if you do the exercises for the stuff you don't know. |
Contribute!
For this team, our motto is:
“Ambition drives success” - Not (Not) Dylan Donahue, 2023
meaning that you truly get out what you put into the team. The typical ask for weekly contribution is around 5 hours for regular members, but people who go beyond typically get more experience/system knowledge and really get to feel like a part of the team.For some projects, GitHub Issues is used to track tickets. For others, there might be a different way of tracking tasks/tickets/issues.
...
Talk to your lead/head if you’re looking for things to do!