Today is the first day of our new Gecomputation and Spatial Analysis (GSA) pathway on our undergraduate degree. Over the summer Jon Reades, Naru Shiode and I have been developing module material and today we (well, Jon and I) finally get to use it with our students. We provide a very brief overview of the pathway on the About page of this website, but I thought today is opportune moment to discuss it in a little more depth.
How many times do you return from field work or a holiday to find that most of your first day is spent deleting emails that are no longer applicable or were never relevant to begin with? Or, worse, you are asked to address issue ‘x’ but have no history or documentation to explain how ‘x’ became a problem, what solutions have been considered, or even why you are the one to solve it! Asana and Slack can help with that.
As we prepare to teach the first year of the GSA pathway, we’ve been experimenting with techniques more commonly used in software development to see if they can help us to deliver quality and integration in our new modules right from the start. This post will explore the logic of Pair Programming.