For this past week’s overview, I put most of my focus working on my midterm with a web developer. Overall, the experience was interesting. I was probably a bit too shy and awkward initially since I was the one leading the conversation and was not really sure where to start the conversation. It was reassuring to go over the rest of the class’s midterms with their own developers as well. It ended up going well and, despite my initial kind of confusion, I felt reassured afterward that it was not necessarily just me feeling lost. It is common for everyone, but sometimes I just think that my natural thought process does not function in a natural web developer process, so I have to check myself before I start a task and plan things out more efficiently.
As for last week’s discussion with Laura while she was substituting, we definitely covered the agile manifesto and the sort of chain of command that takes place in different work environments that web developers are a part of. While some are more beneficial than others depending on the workload, number of participants in a group and so forth, it was interesting to see such how there are many distinct structures in the work environment taking place.
Circling back to my web developer profile for the midterm, I was not surprised at all to learn that Emmett Jacobs had come from a deep-seeded interest in computers and technology. This kind of lead me to believe that yeah, this is something that I would be too late to take an interest in and such. However, after we went over everyone else’s midterms in class I was surprised to learn that a couple our our classmates had talked to people who still didn’t consider themselves “real” web developers due to their late start.
We discussed in class why some of us had problems opening the file we created for homework last week. We needed to make sure that the PHP is opened in the server not in the browser. We also discussed the agile development process and the concept of waterfall. The concept lies in the idea that different teams work together at different stages and the work flows between the channels. However, there were many issues with that methodology. The agile manifesto came about to solve the problem occurring in the waterfall methodology. They created a way of how software should be developed. The most efficient and effective method of sharing information and development of a team is face-to-face conversation. This goes against the new trend of tele-work and how agile does not work within that trend.
The double diamond concept of design was also discussed in class. Usually we look at the first problem then get solutions, but we should look at both diamonds and look at every angle before coming up with solutions. When we work on one thing, we delve deep into it and forget to look at the overall macro level of the project.
I finalized my developer profile. I enjoyed working on mine and getting to know a person in the web development field. I also learned that you can start and get yourself into this field whenever and it is never too late. It is also important to try something out before assuming you will not enjoy it or be good at it. In the case of my developer, he had no idea he would be interested in software development and after taking a random course, he realized that it is where his passion lies and what he wants to do in his life. I also got the chance to read other profiles and learn more about other developers.
The tutorial about command line was descriptive. Programs are made up of layers which result in the final nice looking version. It is a very cool way of handling things and documents on your computer. You give your computer demands, which are passed on to the computer system to run. We can navigate through our computer the way we use Finder on Mac. We should always be careful of any commands we can give because we could mess up our computer system or wipe it out with one simple command.
What resonated with me the most this week was stated in the Agile Manifesto:
“Simplicity–the art of maximizing the amount of work not done–is essential.”
I want to be able to continue thinking like this as I approach both the final project and future web/digital projects. I tend to overthink things and get bogged down in the granular tactics instead of focusing on the big picture. I overcomplicate and get frustrated. I have to learn to be flexible, take a step back and look at the project as a whole in order to be as successful as I can be.
The Agile Best Practices video had great concepts that I think can be translated for any managing any project—planning, feedback and testing. For the final project, I will need to create a plan, ask my classmates for feedback and continue testing for the user on the front and back-end.
Updates on the final project: I had SO much trouble getting my site to be hosted on my server on my computer. I did see that it slowed my computer down a little bit, but it was not anything too significant. However, I have not had as much time to go into the code and begin updating it to fit my needs. I’ve begun taking pictures, short video clips, and creating content for the site, since I think that will be the easiest portion of the project. Moving forward, I hope to use a more efficient project management tool to keep me on track of small things I can do every day to alleviate the workload and added stress as we finish up the summer semester. Something I hope to be able to keep in mind is looking beyond the front-end and UX of my site and approach the customizations with a problem-solving lens, as explained in our reading.