The principles behind the agile manifesto reminds me of a graphic design event I participated in last semester where a number of professionals (trained in the university and self-taught) shared their common experiences with clients and expectations. They essentially pointed to these as the three tentpoles for successful projects:
- Clients and developers working daily throughout the process and communicating face-to-face as much as possible (As opposed to just the start and final moments)
- Building projects around motivated individuals. Having an enthusiastic (and understanding) attitude when considering the necessary granular work for a project is going to keep most developers from quitting.
- Working simply and building on working software in small steps while communicating clearly the short term goals that have been met along the way.
That same event was effective in demystifying the magical “in between” the start and finish of projects. Standing with the aforementioned tentpoles as a foundation and communicating what what has been done before, what’s possible and what we could “try,” in the most straightforward, logical way brings every difficult project into a better perspective.
It was also helpful to go through the qualities of the Twenty Seventeen theme. It’s also a great coincidence that we’re on the subject of adding autoplay video/audio to the front page of a website as MySpace recently experienced its massive loss of songs added (generally on the front page). Overall, I am excited to continue adding to my personal website.
I’m still trying to learn the merits of PHP working within HTML (and needing a server) as opposed to linking to a JavaScript document, and I believe I’ll have to go through the previous assignment with some assistance (which I wrote natively and added as one commit when I realized later it should have been multiple granular edits along the way).