No description
- Python 95.9%
- Nix 4.1%
Update readme to include python path guideline See merge request ee2l1/2025-2026/b.h.01/hearth-localization!6 |
||
|---|---|---|
| m1 | ||
| m2 | ||
| m3 | ||
| m4 | ||
| samples | ||
| .envrc | ||
| .gitignore | ||
| devenv.lock | ||
| devenv.nix | ||
| devenv.yaml | ||
| README.md | ||
EE-IP3-BH01
Coding guidelines
- Every function should document what the inputs and outputs are using comments
- Function and variable names should follow the snake_case format
- Keep the architecture horizontal: Try to avoid nested functions, keep them parralel.
- Write (multiple) tests for a function
- One function should do one job. If a function does multiple things, split the function into mulitple functions.
- Try to keep functions short (max x lines)
- A maximum indentation of x is preffered
- Document desiscions made
- A feature should first be made in a branch. Later can be merged into main
- AI can be used as a search engine. Not a replacement.
- Every file path should use the python
Pathfunction frompathlib
Report guidelins
- Every table, figure and equation needs a label.
- Label should be of ":-"
- Check grammer
- AI can be used as for short phrases
Human guidelines
- Short meetings at start of lab.
- Be on time for a lab
- If you cannot be on time, let it know.
- Keep each other up to date.