Project Management

Tasks This Week:

Group assignments:

Individual assignments:

Reduced Process This Week:

Below, I walk through some of the notes/screenshots that I have from my work this week and explain my thought process as I was completing my assignments.

For the project this week, I refamiliarized myself with the linux/git syntax and I began to formulate ideas for my final project. As noted here, I am, currently, planning to create a some kind of musical instrument that reacts to touch to create a synthesized tone sending an output to both a smaller onboard speaker and a 1/4" standard audio output.

1. Little to report for this week in terms of what I used as resources. Mainly used basic HTML, CSS, and JS pages from W3school as seen here. Although I had fairly little time to put my own personal touches on my web design, I had a chance to walk through some ideas for my final project and start taking diligent notes on my final project. I am excited that for my final project I have started the CAD process.
   Here are some of the tools that I use already or have some experience with:
   • HTML(5)
   • Python
   • CSS
   • JS
   • C++
   • Atom IDE
2. In starting to put together my final project, I used OnShape to start modelling a shape for a shell for a MIDI controller.
3. This week, I also got more and more familiar with git. Even though I already had some experience going in there were still some points on which I needed to be refreshed. For posterity, I will put here the steps to get the git repo set up on a local machine, and the steps to push changes:
   1. Open Terminal
   2. Use the following commands to navigate directories:
      • ls = shows what's in the current folder
      • cd foldername = goes into a folder with the name foldername
      • cd ../ = goes up a directory into the folder above in the hierarchy that contains the current folder
      • mkdir directoryname = makes a new folder within the current folder, and n ames that new folder as "directoryname"
   3. Check that you have git, by typing the following into the Terminal line (if on Mac) git --version
   4. Clone the class webpage. Go to GitLabs, click the Clone button, and then copy the https authentication ersion. In the command line, type in the following:
      • git clone "pathcopied"
   5. Use "cd foldername" command to navigate step by step into your personal folder
   6. Make your website files and paste them into the proper folder
   7. Now, type in the following lines into the terminal and press the enter button after each line:
      • git status
      • git add
      • git pull
      • git commit -m "commit comment"
      • git push

1. Be even more familiar with git before starting - although sort of a funny suggestion having more experience with git before the class would've been useful. Although, I will say that I felt like I had a relatively easy time getting started given my background - I would've been somewhat unhappy starting off with no experience in git.
2. Zach in Retrospective here: Another improvement/change that I would make would be to approach the final project even more solidly. Although I think I did a relatively good job finding some specific details to work with for my final project, had I taken the time to look through each of the weeks and think ahead about implementing each of them as a piece of the final project, I think that I would be in an even better spot than I am right now.
3. Zach in Retrospective here (again): I would have appreciated if I had decided on a specific website construction better ahead of time. I have spent a looooooooong time fixing, updating, and changing the structure of my website to match what I need it to do; having some of that work done ahead of time would've saved me a lot of headache.

1. One of the biggest conclusions that I can take away from W01 is to be as on top of everything as I can be. Making sure that assignments are done on time, keeping up with documentation, etc. Although things will inevitably happen that will necessitate a change in plans, trying my best to keep on top of everything will allow the rest of the course to be as smooth as possible.
2. Maintaining the structure of the website and adjusting my current plans will happen. Even if I think that my website will end up being one thing, I should try to be as flexible as possible and let things happen in the course that may adjust the way that I want to present information, share my progress, and more. As one of my good friends says, "always be ready to adjust your sails" for whatever life throws at you.
3. Really try to embrace the spiral design thinking structure. This goes back to point 2. but always be thinking about how a current design will translate into a later design, how you can learn from failures, and how processes can be changed in order to have a better workflow.
   • Specifically this week, if I were to do everything over again, and make a change to my workflow, I would try to make sure that each change to a file/note/piece of work/evidence that I am making is reflected somewhere on the website as soon as I do it. Zach in retrospect again here, but this would save a me a ton of headache later that was pretty unnecessary; "When work is happening, documentation is happening." would be a wise mantra to follow.

1. Git Tutorial 1
2. Git Tutorial 2
3. Flowchart Maker
4. OnShape - Online CAD Software