> For the complete documentation index, see [llms.txt](https://avionics.rocketcommand.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://avionics.rocketcommand.org/culture.md). # Culture ### Core Values In Avionics, our core tenet is "education through innovation." Everyone's learning all-new things at the same time, so curiosity and ambition usually matter more than existing experience when it comes to new ideas. Don't let experience stop you from challenging "it's always been this way" thinking. If you see something that doesn't work or could be better, bring it up. Always start with the product story. Work out the user experience before you touch anything technical. Never start with a technology and work backwards to find a problem it can solve. ### Structure & Roles Avionics touches multiple areas, and people often work across them. That said, work generally falls into a few areas: Hardware, Industrial, Software, and Integration. We encourage you to explore them all your first year before focusing on a specific field. Every project also has directly responsible individuals (DRIs) for each major engineering domain and the top-level. DRIs are chosen based on experience to both work on and manage the work of other contributors within that domain. Leads set the overall trajectory of the subteam and interface with the broader team on mission requirements. DRIs own execution within a domain, keeping the day-to-day work on track and the people in it supported. A lead may also be the DRI for a domain they're closely involved in, but the two hats stay distinct: when they're acting as DRI, they're accountable for that domain's execution; when they're acting as lead, they're making calls about the project or club as a whole. Like industry, being a DRI is an impressive project role, but comes with the added responsibility and accountability of keeping a project on track. Gaining experience as a DRI is a great way to market yourself for an elected leadership position. ### Team Dynamics This team prides itself on the unique skills each person brings. Ask each other questions, share knowledge, teach what you learn. No one's expected to know everything, so lean on each other. Look to leads for direction and DRIs for domain-level questions. Leads are weighing things you may not see yet, like system-wide planning and mission requirements. If you're uncertain about a direction or have concerns, ask before abandoning it or changing course on your own. Leads, including retired ones, are also mentors, not just decision-makers. They've been where you are and are a well of advice on everything from technical problems to career, so don't hesitate to lean on them for more than just direction. As the year's launches and social events go on, this subteam tends to grow from a technical community into a social one. We hope Avionics becomes like a second family that keeps feedback professional, never personal. ### Engineering Ethos Reliability is what separates a rocket from a missile. Default to the simplest solution. If something's harder to understand, test, or debug, it needs real justification. If something isn't tested, it doesn't work. Design for failure: expect edge cases and people making mistakes, and build so the system holds up anyway. Talk to other subteams early and often. It's easy to assume everyone's working from the same understanding of a spec, and it's almost never true. ### Work Standards Every task needs an owner, who keeps their work visible and moving. If you're blocked, surface it to a lead early. All designs, code, and hardware changes get reviewed before integration. We value consistency over heroics: steady, communicated progress matters more than last-minute effort. The deadline is still the ultimate inspiration. There's nothing wrong with fixing something you know is broken on the launch field. No question is too small or embarrassing to ask. Asking prevents wasted effort and rework later. If you're building off an old report, check with someone before copying it verbatim. ### Accountability Accountability is shared. If you're given work, you're supported in doing it, and in return, we ask you to communicate openly as you go. DRIs carry more of that weight, which makes that same openness even more important. If you are held accountable for a mistake, it's nothing to kill yourself over. Mistakes are guaranteed in engineering, but learning from them isn't. Everything will work out in the end, or just make a good story if it doesn't. That support goes both ways. If workload, exams, or life outside Avionics is affecting your ability to contribute, tell us early so we can help you find room to breathe. You are encouraged to block off a week for an L1/L2/L3 certification rocket instead of attending work sessions, so long as you communicate ahead of time. And if an emergency comes up, take the leave you need without notice. ### Health and Safety Above everything else, we protect safety and team well-being. Follow the Safety Officer's procedures, no exceptions. Motors, pyrotechnics, and armed flight hardware always need supervision. If something feels off, even if you're not in actual danger, tell a lead.