Task3 Development Process
Thus far, the development process for Task3 has been slow, but steady. Life without an API is often challenging, but it is really satisfying to create code that works without the 'crutch' of the API: I feel that I really have to possess a much deeper understanding of how the code works in order to alter it.
For this phase of the project, I contributed in a variety of ways. From the development angle, my team and I all brainstormed to determine strategies for the various implementation features of Task3. We set goals, and broke down responsibilities on how to meet those goals.
I contributed to the implementation of the scrolling menu of tasks, as well as designed and created the task icons (all 9 of them, one for each task status). Here, I focused on readability, and went through several iterations before I found a text, color, and information combination that was legible from such a small window as is present on the sifteo cubes.
I created all of my team's documentation for this phase of the project, including our powerpoint presentation, photos, videos (excluding the demo of the label changing color), and annotated photos doc. I did not spend as much time working with the code itself in this phase, something I would like to change for the next phase of the project: the portion I did create is crucial to the functioning of the project, but a deeper dive would be beneficial to both my team and myself as a programmer.
It was challenging coding the cubes without an API, and in a language that I have never seen or used before. There was a lot of educated guess and check required regarding syntax. The largest struggle is always when the programmer knows what needs done, but can't find the syntax to do it.
For the future, I would like to work on cleaning up the code we have, and finishing the final features of our project!
