The AffectRE’19 workshop on Affective Awareness in Requirements Engineering finally took place on Tuesday, September 23rd after being rescheduled due to the Tapah Typhoon. Despite the bad weather which made Jeju island hard to reach, 20–25 people were present during the workshop.The first part of the workshop saw one invited talk, followed by five interesting paper presentations, and a highly interactive discussion during the second part.
During the invited talk, Jan Ole Johanssen (Technical University of Munich) presented a framework for the continuous understanding of users’ tacit feedback during software evolution tasks. …
A great deal of academic career is getting comfortable with rejections (and understanding selection and survivorship bias).
In this post, I have prepared a (possibly incomplete) list of journals, conferences, grants, and job applications for which I have been rejected. This post is inspired by prof. Jessica Vitak CV of Failures.
(Note: this is a long post)
I was invited to give a talk at this year’s International Symposium on Reliability Engineering (ISSRE2017) doctoral symposium.
It was quite a new experience since it gave me the opportunity to reflect upon my Ph.D. one year after completion and being on the other side of the fence after attending two symposia as a student.
The organizers did an excellent job in mixing the point-of-views of a junior researcher (aka me) with the one of a senior, Lionel Briand contributing to the success of the event that doubled the expected participants and was praised…
The long way ahead
Surveys among millennials indicate sustainability as one of their first priority, for example, when deciding on a purchase.
I believe it would be interesting to know whether this belief also holds for how millennials see the academic curricula, in particular, the software engineering one.
In fact, in the last few years a trend towards including sustainability and in particular *greenability* topics in the traditional software engineering curricula.
The definition of sustainability which I prefer in this context is the one offered by the United Nations:
Meeting the needs of the present without compromising the ability of…
I have recently defended my Ph.D. Here’s a small retrospective with some facts and figures.
In social sciences they say that the existing differences among the participants to an experiment is as important as the difference due to the treatment.
In software engineering the differences are usually the existing skills and experience, in particular software development skills.
Quoting Steve Freeman, “no tool nor technique can survive inadequately trained developers”. This is evident for a technique like TDD.
So lately I have been interested in studying the people’s skill factor, and set part of my research agenda in understanding what are the necessary skills that can make the best out of TDD.
If you read the…
I often need to know approximately how many words my paper contains (for example when asking a quote from a proofreading service). As opposed to MS Word, getting an estimate word count in LateX is not that easy. Today, I stumbled upon a command line utility bundle with the standard TeX distribuition: detex.
The utility just strips TeX commands from a .tex file. So a simply way to get a word count for the paper is:
detex file.tex | wc -w
Next step, include the command in the vim-latex plugin (yes, I do use VIm, at least most of the time) to have the word count shown in the status line.
Originally published at dfucci.co on August 10, 2015.
I have been ranting for sometimes now about how scientific knowledge is actually produced in SE. To be completely honest my rants are due to a bad, unexpected rejection.
Yes, I am looking at you peer-review, the brittle basis we researchers trust to carry-out our endeavours. I guess my issues with peer-review reached an all time high after stumbling upon two articles within few days.
The first is an experiment made within the NIPS (the most important machine learning conference) reviewers committee. They (artificially) created two independent committees and tasked them with the same acceptance rate. Turns out that the…
And also for this year, the Academic Writing Month (aka November, aka November) is over.
My pledge at the beginning of the month was 10 pomodoros (the accepted measure of academic productivity) a day, 5 days a week.
This would sum up to 10 x 5 x 4 = 200 pomodoros.
The reality is way different. The actual number of pomodoros I completed (i.e.; 25 minutes of work, straight and without distractions) was 104, distributed as follows
During last ESEM I have stored the conference related tweets for a small data analysis. Let’s see what the results say.
Food enthusiast (poorly on a diet) stuck in the body of a Software Craftsmanship researcher @unihh. Southerner, football fanatic, wannabe ukulele player