Academic Marginalia

"Unboxing responsible requirements engineering" In December 2023, I attended the ESEC/FSE conference in San Francisco, and in addition to hearing about lots of interesting work relating to human aspects of software engineering, and security, I also enjoyed listening to the keynote talks delivered at the event. I already shared some reflections on one of these keynotes in a previous blog post ( GenAI for Software Engineering ) and in this one I cover my notes on another keynote which was delivered by Professor Margaret Burnett, a University Distinguished Professor from Oregon State.  Her talk was titled " Getting outside the Bug Boxes " and highlighted the importance of distinguishing between the goals (or policies) of software engineering from the mechanisms (or tools and methods) used to engineer software. The central thesis was that, too often, software engineers constrain themselves inside a box that is based on the latter and therefore miss important aspects of

Reflections on academic leadership ... In Dec 2017, I had just been appointed Head of the School and asked a wise colleague for guidance on meeting the challenges of the role. Knowing that I am a film buff, she gave me a copy of a movie called "Thirteen Days" (2001) together with a brief note highlighting some key leadership behaviours that she felt were important to learn. At the time, I noted the key points she had written but never actually got around to watching the movie - mainly because it was on a DVD and we no longer had a player in the house!  I completed my tenure in the role, with some successes but also faced several challenging situations.  My colleague's advice was useful when faced with particular challenges, but I also found a need to adapt some aspects of the guidance to fit my personality and style. Six years later, as we approach the end of 2023, I noticed that "Thirteen Days" was available on one of the streaming services we subscribe to and

Will AI agents become integral members of software engineering teams? I recently attended the ESEC/FSE conference in San Francisco, where one of the keynote talks was titled " Towards AI-driven software development: challenges and lessons from the field " and delivered by Professor Eran Yahav from Technion. This post summarises my notes on the key messages of the talk. Part of the context for the talk was a recognition that generative artificial intelligence (GenAI) technologies are seeing increasing usage across all stages of the software development lifecycle. Of course, the extent to which they are used is not uniform across all stages, with the most significant usage being for code and test generation. However, as demonstrated by some of the papers presented in other sessions of the conference, the step change in capability realised by the public release of LLMs over the past year has led to researchers exploring the use of GenAI in deployment and maintenance scenarios, f

As another year draws to a close, I find myself reflecting on the experience of the 12 months just gone and what could be learned for the year ahead. One of the features of the past year was how my interactions with colleagues, friends, and family transitioned from being mostly online to a ‘hybrid’ mode of engagement. My experience of hybrid varied from alternating between online and in-person interactions with people, to attending gatherings where there were a mixture of online and in-person participants.  The different activities I was involved in over the year highlighted the different ways in which having presence and being present play a more significant role in our interactions that the modality of the engagements themselves. Here I am distinguishing different types of hybrid interaction by considering the dimensions of time and space. Sometimes an interaction is hybrid because it depends on people being together at the same time, but distributed in different places (some co-loca

Content warning: mental health, anxiety,  depression. I have just finished reading "Managing Your Mental Health During Your PhD — A Survival Guide" by Dr. Zoë J. Ayres, which is an important resource for PhD students and supervisors.  It is definitely a book that I wish was available when I did my own PhD and I am writing this review to help highlight why it is a useful addition to the resources we use in supporting PhD students. Completing a doctoral research project, writing up and defending a thesis with the goal of being awarded a PhD can be a challenging undertaking and it is not unusual for a students to experience some downs (and ups) in their mental health. This was certainly my experience, where my mental health went through all of the following at different stages of the process:  disorientation as I moved from industry to academia; a sense of accomplishment when I presented my first paper at a workshop; anxiety as I felt unsure of whether my work was good enough; 

“When will I be done?” - in a busy working life, with lots of tasks demanding our time, this is a question that arises from time to time.  In the break from work at the end of another year, I am reminded to reflect on the things that I have done and a particular conversation with a group of friends where we discussed what “being done” means to us. The discussion explored the role of different goals in our lives and what we each defined as the point of having freedom from obligations to do what we want. Some of the common themes related to the independence of our children and retirement from work. I also noted a sense that all of us felt that we were really busy right now, and there were plenty of things on the horizon that would also need our attention in the next month or so, but ‘things would get better after that’. This is a recurring theme I have observed both within myself and among colleagues and from other academics who share experiences online. Of course the reality of our si

My out of office message in on, my inbox is empty ... Image by Solen Feyissa from Pixabay My out of office message is on, my inbox is empty ... and mesmerised by Microsoft's floating balloon animation, I thought of writing about how I got here. Keeping up with all the information, requests for action and questions that flow into our email inboxes often seems a losing battle, but it doesn’t have to be so. It is increasingly common to see colleagues share their victory over the deluge of messages by reaching “Inbox Zero” and it is something I have improved my ability to do over the past couple of years.  I don’t always get to zero every day or week, but I can often get to below 10 messages to deal with, and even hit zero from time to time. My method is similar to that adopted by others, but I thought of documenting it here as a way for me to refer to it in the future, and also in case it helps others. Unread e-mails result https://t.co/DdB3jZJ3pp pic.twitter.com/q7hoTFHCUi — PHD