Reflection

Lessons Learned

Label components with their values on the schematic to help with organization and board populating.
Be specific about sensor values in software proposals.
When selecting a microcontroller, carefully read the specifications to ensure it has the necessary capabilities for the project.
Update project files as changes are made to facilitate understanding by peers.
Communication is critical in group projects to stay on track and ensure tasks are completed.
Organize the software diagram logically for clarity.
Use indicator LEDs on subsystems to test their functionality during PCB board population.
Order multiples of components in case of breakage or loss.
Keep track of deadlines and create a schedule for the team.
Complete assignments beforehand for time to review and fix errors before submission.

Pay close attention to details and be precise in your work, especially when it comes to labeling components and specifying values.
Communication is key to success in group projects, so make sure to keep in touch with your team regularly.
Keep your project files organized and updated to make it easier for peers to understand your work.
When selecting components, be sure to order multiples in case of loss or breakage.
Follow a schedule and keep track of deadlines to avoid rushing work.
Review and double-check your work before submission to catch any errors or mistakes.
Breaking larger assignments into smaller tasks and setting deadlines for each one.
Identifying potential obstacles or conflicts ahead of time and coming up with strategies to address them.
Implementing feedback from the teaching team in a timely fashion.