Reflection of midterm and agile

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.

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.