.png)
Gabriel Journal Entries:
Week 1:
The beginning of this week was centered around a project tangential to the PuzzleIt: an autonomous car. After completing that, I began creating the Gantt chart for this week. We decided on who would do what, and I was given the System Diagram, as well as helping out on the Socials front. After a slight modification to the diagram shown in our presentation last semester, I uploaded it to the group Drive. After finishing a short video, the week had ended.
Week 2:
This week started with working on the pseudocode. Given the amount of individual objects needed to be coded, this took a bit longer than expected. However, I found a shortcut: I would simply change one segment of “general” code used for all modules with code specific to the individual modules. This shortcut was also used on the programming flowchart. Throughout the middle of the week, I would alternate between working on the flowchart and ordering the parts needed for construction. After finishing the flowchart, the week ended.
Week 3:
This week started with dividing the workload between us, as shown in the Gantt chart. I chose to finish the GCC (Goals, Criteria, Constraints) for the PuzzleIt, as well as spreading our surveys to every parent we knew. I feel as though I could have done more for our group this week, and I hope to reflect that in the upcoming weeks. As the week came to a close, the survey answers just barely surpassed our set goal of 100 responses from parents.
Week 4:
This week started with the completion of the Estimated Market document. After a day of compiling resources to calculate our target market population, I gathered the data and placed it on the document, while still keeping a more casual tone for the average reader. After linking the sources and double-checking the profit margins, I wrote the formula in words, before calculating the result. After closing this document, the week had ended.
Week 5:
This week, shortened by the P-ACT, mainly consisted of scriptwriting and planning for the future development of the PuzzleIt business. I corrected the error in last week’s work, that being the lack of timing for profits. The prototype model of the Color Boop module had finished printing, in the form of white PLA. We began working on the script for our elevator pitch, keeping the tone nonchalant, if not unprofessional. As the tab closed with a completed script, the week had ended.
Week 6:
This week finally began my contribution to the project as the Chief Software Engineer. I spent this week designing the code for the Color Boop, Color Press / Light-up Safari, and CopyCat modules. After finishing and bug testing those, I started and finished the business plan. After one last trial run of the modules, the week ended.
Week 7:
Last week was a failure on my end. I had not finished the code for the modules, and given a school trip this week, I was only able to work for a few days. However, in that time, I corrected my mistakes, both on the coding front and the business side. I recorded the modules functioning, as well as transitioning the business plan to a PowerPoint format. After citing my sources, the highly shortened week had ended.
Week 8:
I spent this week attempting to memorize the pitch and commercial scripts. After filming the commercial, I had planned to make a few edits, but as it was all in one take, it wasn’t necessary. Additionally, I assisted with the construction of the PuzzleIt modules.