Week 7: Version Control & Rapid Ideation 2

(Asadi 2021)

Version Control: Reflections

Version Control is a phenomenon I’ve never explored in detail and not one that I was excited to learn about. Furthermore, after much discussion in our weekly webinar, it transpired that the version control system we were learning about, Git, was generally not admired. Upon attempting the challenge activity for the week, I found the user interface of GitHub Desktop and the terminology used to be very confusing. I initially started questioning what on Earth was wrong with the version history feature in Google Suite or Microsoft Office; then, it became apparent that Git tends to be used by software developers working collaboratively towards a common goal (Guerrero-Higueras et al. 2019). The complex nature of this work holds the potential for a logistical nightmare involving the coordination of contributors and ensuring they’re all using the right version at the right time. A Version Control System (VCS) aims to negate such disruption by monitoring files for changes, recording and timestamping, if any, then allowing users to revisit historical changes or versions as required (Somasundaram 2013).

I was surprised to learn of the various methods Git can be accessed and took some time to attempt both options. One way was to use the desktop software via a graphical user interface (Git Hub Desktop), while the other was to use a Command Prompt-style software (Git Bash) by typing lines of code to execute various actions. Of course, the better of the two is a subjective choice; however, after following a tutorial for the Git Bash method, I had a much better understanding of the inner workings of Git than I did when after trialling Git Hub Desktop.

After researching the topic and gaining a better understanding, I now appreciate that using a purpose-built VCS during complex collaborative projects is pivotal in achieving success. So, despite my initial reservations about the need for a standalone VCS, I’m now of the opinion that while this feature might be helpful when integrated with proprietary software, it doesn’t offer the same flexibility and efficiency as a purpose-built VCS.

---

Spark Forum Activity

Task: Reflect on your previous RI session, detailing what went according to plan and, if anything, what went wrong.

Entering the second bout of rapid ideation, I’m keen not to waste time and want to get my thoughts down thick and fast. In the first rapid ideation session, I'd done this too but had spread my ideas across different mediums, like scrap paper, a sketchbook, iPhone notes, Google Docs and Google Keep. As you can imagine, this ended up driving me crazy because I had all these great ideas, but they were sporadically generated and in no way organised. As such, I intend on taking a more streamlined approach for the second rapid ideation and will try my best to organise my Google Drive with folders and properly named files.

A recurring discussion among my peers surrounds time being a finite resource while managing other aspects of life as well as this course. I'm looking forward to working in groups later in the programme; however, for the second rapid ideation, I need it to be a sole mission while I get to grips with my new life schedule.

Using Balsamiq during the first rapid ideation was somewhat groundbreaking for me as I’d never used a tool like it. It has an array of pre-made shapes and graphics that can be quickly dragged and dropped onto the canvas. In theory, although this is meant to help create quick mockups and spend less time on aesthetics, I still found myself making sure everything was properly aligned and looking sharp. As such, in using Balsamiq for the second rapid ideation, I’d like to ensure I create quick mockups and utilise higher fidelity tools, such as Adobe XD or Figma, to focus on the finer details. Furthermore, I plan to better organise my time using Agile practices, such as the kanban board in Trello. I will endeavour to keep my notes better organised in an effort to quickly navigate them during the ideation stages of creating my new artefact.

---

Reflections on RI2

In embarking upon the second rapid ideation session, I set myself the goal of being better organised, using Balsamiq more efficiently and exploring other design software to create higher fidelity mockups. Having established these goals, I find reflection to be a valuable tool to analyse my accomplishments and where I could have done things differently. Firstly, it brings me joy to report that I organised my notes and ideas in one place throughout the ideation stage. I used Google’s Jamboard software, which is essentially a digital whiteboard allowing for virtual sticky and handwritten notes to be stored and presented in one place. I found this particularly useful as I could quickly jot down my ideas and categorise them by assigning colours to the sticky notes.

We had two options for the rapid ideation, one of which related to the controversial Conference of the Parties (COP26), and the other focused on re-modelling others’ or our own prototypes from the first rapid ideation. The completed artefact would then be presented in a short video.

I chose the “COP-out” theme as I enjoyed the graphical prompt (pictured above) and have been fixated on the concept of ideating ever since learning of it at the start of the module. The premise of the theme was to “create an intervention that can be used to raise climate-related issues and/or provide a meaningful positive change from social grass-roots”. As such, I began brainstorming and settled on the idea of creating a platform allowing users a clear picture of their carbon footprint and the factors contributing to it. The first Jamboard page (picture 1, below) was filled with my immediate thoughts and included an array of sticky notes and illustrations that circled the main idea. The second page (picture 2, below) was more refined and examined where the emissions data may come from. Finally, I began creating an app mockup in Balsamiq, although this remains unfinished (picture 3, below).

Upon reflection, I look back on this project with an air of frustration. It started so well, but I hadn’t effectively managed my time and got too caught up in the details. I succeeded in better organising my thoughts and am wholly satisfied with that element; however, I fell victim to scope creep. As per my initial plans, I failed to use Trello and attribute this to running out of time and energy. Although I had all my ideas in one place, I simply kept adding, refining and editing them, which led me to become overwhelmed by the ever-growing project in front of me. My hopes of utilising Adobe XD and Figma dissipated, along with the time I thought would be sufficient to complete the project. Essentially, I lost interest, lacked energy, and regretted not investing more time in scope planning with Trello. With that said, I’m so glad to have experienced failure in this way and feel better prepared for similar situations going forward. I’ve since had the time to explore the benefits of Kanban boards and have already begun formulating one to support my course-related tasks. I’m a firm believer in planning for success; however, I feel that my excitement toward the ideation stage clouded my judgement and led to failure.

---

References

ASADI, Elnaz. 2021. Photo by Elnaz Asadi on Unsplash. Available at: https://unsplash.com/photos/GC_MO-vOa3s [accessed 20 Jan 2022].

GUERRERO-HIGUERAS, Ángel Manuel et al. 2019. ‘Predicting Academic Success through Students’ Interaction with Version Control Systems’. Open Computer Science 9(1), 243–51.

SOMASUNDARAM, Ravishankar. 2013. Git: Version Control for Everyone, Beginner’s Guide. Birmingham: Packt Pub. Available at: https://www.vlebooks.com/Product/Index/623523?page=0 [accessed 12 Jan 2022].