In the most recent CACM editor’s letter, Moshe Vardi, the CACM’s editor-in-chief, addresses the question of open access from the perspective of the ACM . The ACM is a non-profit organization for (mostly) computer scientists, and a publisher of conference proceedings and journals.
I find the editorial rather disconcerting. Vardi views “the open access movement” as being in “the IP communist camp”. There are so many things wrong this terminology. For one, I didn’t know there was one open access movement; I see many different streams of activity. Then, using 19th century terminology like communists and capitalists isn’t really going to help either; if meant as a provocation it probably achieves its goal, but to what end does this provocation help us? I’m a proponent of open access and most certainly don’t consider myself an “IP communist”. Finally, by pigeonholing well-intentioned efforts as a communist endeavor, it wholly ignores the struggle for new and innovative models of publishing research.
Aufruf zur Einreichung von Beiträgen für den Software-Engineering-Ideen-Track der SE 2015. (Ich bin der Programkomiteevorsitzende.)
Über die SE 2015 und den SEI-Track
Die Software-Engineering-Tagung ist das wichtigste jährliche Treffen der Software-Engineering-Community im deutschsprachigen Raum. Ein besonderer Schwerpunkt der SE 2015 ist das Thema “Sichere cyber-physikalische Systeme”.
Das Ziel des Software-Engineering-Ideen-Tracks ist, ein Forum für die Präsentation von vielversprechenden Ideen und Innovationen im Bereich des Software-Engineering bereitzustellen, welche noch nicht vollständig implementiert oder evaluiert wurden. Die Beiträge können eine Forschungsidee, erste Resultate einer Dißertation oder eine formativ durchgeführte Fallstudie präsentieren, wobei der Bezug auf ein zukünftiges Forschungsfeld, ein neuartiges Werkzeug, eine neue Methode oder die neuartige Zusammenarbeit mit anderen Disziplinen erkennbar sein sollte.
I’ll be keynoting the European Conference on Software Engineering Education on Nov 28, 2014, at 11:00 Uhr, at Seeon Monastery, Germany. Here is the abstract. See you at the conference!
Over the last few years, we have shifted most of our courses from traditional upfront lecturing to project-based learning. Each course consists of multiple projects with three main stakeholders: students, teachers, and industry. Using AMOS, our “agile methods and open source” software engineering course as the example, we review our course concept and discuss our experiences. We take the perspectives of the three stakeholders in turn: Achieving learning goals and performing meaningful work (students), fulfilling both an educational and an economic mission (university), and receiving a return on time and monetary investment (industry). The perhaps surprising result is that these three perspectives can work together well and make reaching each stakeholder’s goal easier.
We recently discussed our approach on my research group’s website as the “Lehrkonzept der Praktischen Softwaretechnik an der FAU” (in German).
I’ll be keynoting the 16th KKIO Software Engineering Conference on Sept 22, 2014, in Posnan, Poland. Here is the abstract. See you at the conference!
MySQL was sold for one billion US-dollar. Red Hat is worth a multiple of that. The Eclipse Foundation has pushed many software tool vendors out of business. How come that open source, a phenomenon dubbed “temporary” not only has become sustainable but the business strategy of choice? In this talk, I discuss the four main business models, two for-profit and two not-for-profit, that have made open source sustainable. These models are changing the business of software and the future of our industry.
The talk “The Open Source Software Developer Career and its Benefits”, which I gave at the 2014 Entwicklertag in Karlsruhe earlier this year, is now fully documented. You can take a look at the original paper, talk slides, event photos, and finally (woohoo!) a quality video recording courtesy of Andrena, the organizers of the Entwicklertag. For simplicity’s sake, below please find an embedded Youtube video (local copy).
An old debate has recently been rearing its ugly head: the value of standards in IT and the role of open source. In my view, it is really very simple. There are two types of standards, and they determine the role that open source can play.
- There is a type of standard (type 1) where vendors truly want to collaborate (let’s call it an “honest standard”), and then
- there is a type of standard (type 2) where vendors do not want to collaborate and create a standard only to satisfy politicians and/or the public.
The U.S. president Barack Obama wants to learn programming and so does former New York City major Michael Bloomberg. Germany’s chancelor Angela Merkel does not, but reports tell us that her cell phone connection was spied on by the U.S.A. As long as it doesn’t turn out to specifically have been Barrack Obama’s code which cracked Angela Merkel’s cell phone, I’ll stay out of politics and focus on the question: Should you learn to code?
The short answer: No. Don’t waste your time.
The long answer: It depends on your age and your goals.
The confusion arises from different goals you might have for learning how to program. I see the following possible reasons one might want to learn coding: