104
edits
User:Jeffrey Fisher/2023 Feedback Session Brainstorming: Difference between revisions
User:Jeffrey Fisher/2023 Feedback Session Brainstorming (edit)
Revision as of 22:28, 21 December 2023
, 21 December 2023no edit summary
No edit summary |
No edit summary |
||
|
= Questions =
==
== Onboarding ==
* What were some of the most confusing/annoying things/topics?
* Did you feel you had enough support from the leads?
* What are your opinions on the overall format? (written materials/tutorials, project progression, independent work with leads available to help and answer questions)
= Brainstorming =
== Feedback stream of consciousness ==
=== 3rd meeting time ===
* 2 meetings = 4 hours per week. 4 hrs/week * 15 weeks = 60 hours per semester. That's 1.5 full-time work weeks.
* Three 2-hr meetings would bring it up to 6 hrs/week --> 90 hours per semester. Which is 2 full-time work weeks.
=== How do we merge the 3 groups (Clark, NBRF, RAL)? ===
* If we can get the Clark room reserved all semester again, that could be quite nice. Could probably fit software + electrical.
** Not sure if mechanical can work effectively in Clark. They may need tools that we own, which could be annoying to carry.
* Clark has fit all catamaran members pretty well.
** Having our own private-ish space would be ideal though. Also tools access?
* RAL is medium-sized. Might not be able to fit everyone. However the rest of IDEA may be okay? We've met there before. However software team has grown a bit, so that might not work well.
* Software can probably meet wherever / with electrical and only go to NBRF for pool tests.
=== Monthly all hands meeting ===
* idea: Just present what there is to present?
** Not everyone presents every time, but hopefully a good enough rate that we always have something to present. More in-depth presentations.
=== Stricter deadlines ===
* My conception of this boils down to: "be honest". Not looking for superhuman work pace, and of course it is an extracurricular even if can be more intense than some.
** Come up with a plan. Feels good to check things off, and useful to have an overview of what is coming next.
** The plan should include estimates of how long things will take, and self-prescribed deadlines.
** Accountability. Awareness of when projects go off-plan.
** If we are coming up on a deadline, or miss a deadline, re-evaluate. Be honest about how much time we have. If something takes longer than we expected, the plan likely needs to be changed.
*** Cut things out of the plan. Move them to "extra". Shrink the minimum viable product.
*** Ruthlessly shrink the core plan. It's better to have something that partially works, that is partially tested, than to have nothing at all.
** Incremental plans. Continuous testing.
*** Try to reduce integration hell.
*** On software side, merge frequently. Avoid long-running branches when possible, and try to have long-running branches frequently integrate code from main so that we are always running with as much code connected as possible. Integrate incrementally over time, rather than in a massive integration hell.
=== Hangout more ===
=== How did onboarding V.1 go? ===
=== General club enrichment ideas ===
== Onboarding stream of conciousness ==
* Likely will switch to Python, that sound good?
| |||