Almost all the engineering decisions are well explained and justified in the 2654E Echo Engineering Notebook. If you have any questions, please take a look at this resource, we hope that it can be valuable for you.
For almost all the code in this codebase there will be or already is explainer videos. If you would be interested in other topics being covered, just contact us!
These aren't necessarily best practices for git, so don't expect these to just work at an internship, but this is what I use for VEX to make sure my code stays reliable.
- Git/GitHub
- Commit every time the code works
- Ensure the main branch is always reliable
- Create branches for each practice or day
- Utilize main branch protection to make sure any changes have to go through the process
- Keep up on git discipline, even though you might be working by yourself, this isn't an excuse to leave your branches a mess and not commit properly/commit directly to main
- Utilize this rich version history to find what has changed
- Video Every Run
If you have any additional questions about the code or our robot, contact one of us with the following ways to contact us:
- Alex Dickhans ([email protected])
- Programmer