Over the last 10 years, I have consistently invited industry speakers to class, to talk about their experiences, to change the pace, and to lighten up the teaching. We recently passed the 100 external speaker mark! (Also includes some academic speakers.) Time to reflect on what makes a good industry talk that enriches student learning.Continue reading “The Art of Inviting Industry Speakers to Class”
Effective writing is important, or you won’t be understood and achieve your goal. An example is to get the ordering of nouns (or adjectives) in enumerations right. Let’s pick an example: In software engineering, a software feature’s implementation should be correct, complete, and testable. So a project goal could be “to ensure correctness, completeness, and testability of feature implementations.”
The following rules apply:Continue reading “On the Ordering of Nouns in Writing”
Over on Facebook of all places, I took part in a short discussion on how, as a researcher, to have an impact on practice. It is not a convenient answer, but in my opinion, if you want to have an impact, you should go into practice yourself. You can also send your students, but this creates a generational lag of research-to-practice transfer that can span decades.
One of the suggestions of how to have an impact was to perform action research. The idea is that you are creating change in an organization where you are performing said action research. However, action research is a research method whose purpose it is to help you build out and evaluate a theory. Unless you are into critical theory, action research does not have, as a primary goal, to change industry. It is just a theory building method.Continue reading “How to Have an Impact as a Software Engineering Researcher”
Many computer science degree programs do a lousy job at teaching science. A high school student, entering university, often has a good idea what science is about, based on their physics and chemistry classes. At least, it involves controlled experiments. At university, this is rarely picked up, and computer science students are given the idea that programming something novel constitutes science. With that idea, they are often bewildered when I teach them rigorous research methods, in particular if those originated in the social sciences (like qualitative interviews or hypothesis-testing surveys).Continue reading “Traditional Theory Building and Validation in (Computer) Science”
There are lots of infographics on the web of how a professor spends their time, and they mostly miss the point. At the core, and after ten years of living it, I feel confident to say that it really is three roles that a professor in Germany has to play to be successful. I also have to say that it is pretty hard to be good at all three of them. These roles are:Continue reading “The Three Hats of a Professor in Germany”
Pay-walled publications are just that: Publications that nobody reads unless someone pays the publisher’s fee. I have no problem with that, because I don’t read pay-walled work and don’t consider it published research and prior art that I should care about.
The real problem starts with researchers and editors who expect me to find, read, and consider pay-walled work as prior art. That’s an unacceptable proposition to me and an unfair one to the world.Continue reading “The Real Problem with Pay-walled Publications”
From current observations, I would like to suggest a new law of hiring professors:
Continue reading “Hiring Machine Learning Professors Fast to Catch-up Short-Term Will Make You Fall Behind Long-Term”
Hiring professors fast to catch-up short-term will make you fall behind long-term.
In software engineering, the structure of research theses, most notably dissertations, is straightforward: (1) Formulate a research question, choose a method, build a theory, then (2) generate at least one interesting hypothesis, choose a method, and test the hypothesis as part of the theory’s attempted validation. A dissertation can do both parts 1 and 2 or just one of them, relying on or leaving stuff to others. The benefit of this structure is that it will be easily recognized by other researchers and make it eas(ier) to write great papers.Continue reading “How Not to Ask Your Research Question (And What to do About it)”
On a whim, I asked my Twitterverse (which includes a fair number of computer scientists) what they think about the following question:
Continue reading “Anecdotal Evidence on the Method Wars”
When peer-reviewing somebody else’s work submitted for publication, what should you do if you find that the authors have a different belief than you about what can be known?
I just had another discussion with a reviewer (by way of an editor) who insisted that I cite (presumably their) work buried behind an Elsevier paywall. How obnoxious can you be?
It is 2019 and there are still editors and reviewers who consider articles, which are not freely accessible on the web, published research? That’s so wrong. Such work has been buried behind a paywall. It yet needs to be published.Continue reading “Pay-walled Research Papers Do Not Constitute Published Work”