Challenges to making software engineering research relevant to industry

I just attend­ed FSE 2016, a lead­ing aca­d­e­mic con­fer­ence on soft­ware engi­neer­ing research. As is en vogue, it had a ses­sion on why so much soft­ware engi­neer­ing research seems so removed from real­i­ty. One obser­va­tion was that aca­d­e­mics toil in areas of lit­tle inter­est to prac­tice, pub­lish­ing one incre­men­tal paper of lit­tle rel­e­vance after anoth­er. Anoth­er obser­va­tion was that as empir­i­cal meth­ods have tak­en hold, much research has become as rig­or­ous as it has become irrel­e­vant.

My answer to why so much soft­ware engi­neer­ing research is irrel­e­vant to prac­tice is as straight­for­ward as it is hard to change. The prob­lem rests in the inter­lock­ing of three main forces that con­spire to keep aca­d­e­mics away from doing inter­est­ing and ulti­mate­ly impact­ful research. The­se forces are:

  • Aca­d­e­mic incen­tive sys­tem
  • Access to rel­e­vant data
  • Research meth­ods com­pe­tence

Con­tin­ue read­ing

Invited Research Talk on Inner Source at FSE 2016

I’m giv­ing an invit­ed research talk (“journal-first”) at FSE 2016 in Seat­tle today, Nov 15, 2016. It is in Ses­sion 5, right after lunch. The under­ly­ing Trans­ac­tions on Soft­ware Engi­neer­ing (TSE) paper is avail­able here. More on inner source here.

Putting on their #Gearface (no Google Daydream)

With all the hoopla on Google Day­dream com­ing up, I thought I’d share two pho­tos of peo­ple high on Samsung’s Gear VR. I think Sam­sung chose a bet­ter name for their pro­duct. The sec­ond pho­to clear­ly shows a per­son with a gear­face. Can’t imag­ing call­ing this a day­dream­face. The future is so bright, you’ll have to wear a mobile.

Mitgründer für Startup mit existierenden Kunden gesucht

Für Uni1 (http://uni1.de) suchen wir mind. einen weit­eren techn. Mit­grün­der (oder frühen Angestell­ten, wenn weniger Risiko gewün­scht ist).

Uni1 will die Zusam­me­nar­beit zwis­chen Unternehmen und Hochschu­len weltweit rev­o­lu­tion­ieren. Uni1 hat bere­its Kun­den und basiert auf einem erprobten Konzept. Wir kön­nen zur Zeit wg. (noch nicht) aus­re­ichen­der Soft­ware­un­ter­stützung lei­der nicht skalieren.

Ide­al wäre ein Full-Stack-Entwickler mit entsprechen­der Erfahrung in Java + Javascript und Web-Technologien. Sozialkom­pe­tenz und die Fähigkeit in einem schnel­len Umfeld zu arbeit­en sind eben­so wichtig. Als Ort ist Berlin oder Nürn­berg ide­al, aber kein Muss.

Bei Inter­esse bit­te Email an mich.

Dirk Riehle, dirk@uni1.de

An Example Charter for Inner Source Programs

Abstract: Inner source soft­ware devel­op­ment is firm-internal soft­ware devel­op­ment that uses the prin­ci­ples of open source soft­ware devel­op­ment to col­lab­o­rate across intra-organizational bound­aries that would oth­er­wise hin­der any such col­lab­o­ra­tion. Inner source breaks down the bar­ri­ers to col­lab­o­ra­tion across devel­op­ment silos by set­ting up an inter­nal ecosys­tem of read­i­ly avail­able soft­ware com­po­nents. To get start­ed with inner source, com­pa­nies need to define their goals and then set up a gov­er­nance struc­ture for an inner source pro­gram and the projects with­in to reach those goals. This gov­er­nance struc­ture is often cod­i­fied in the form of a char­ter doc­u­ment. This tech­ni­cal report presents an exam­ple char­ter for an inner source pro­gram. The goal is for com­pa­nies to be able to copy and adjust this char­ter for their own needs. Towards this pur­pose, the char­ter leaves open the many deci­sions to be made, but out­li­nes the options that any com­pa­ny needs to decide upon when estab­lish­ing an inner source pro­gram.

Key­words: Inner source, inner source char­ter

Ref­er­ence: Riehle, D. (2016). An Exam­ple Char­ter for Inner Source Pro­grams. Friedrich-Alexander-Universität Erlangen-Nürnberg, Dept. of Com­put­er Sci­ence, Tech­ni­cal Reports, CS-2016–05, August 2016.

The paper is avail­able as a PDF file.

Re: Your unsolicited email / our joint problem

To: ana.tackett@orcapr.com, eastonjohnston@iodimpact.com, digitalpragency@gmail.com, RobertP@informationhub.biz, gina@bloc.io, pms990@gmail.com, jillr@blackswansmedia.com, davidf@lfpr.com, khurst@harriswilliams.com, nancyt@vorticom.com, james@planet-dm.com, …

Dear PR pro­fes­sion­al:

With respect to our joint prob­lem, Stan­ford researchers have found a solu­tion!

Please see here for the answer: http://www.scs.stanford.edu/~dm/home/papers/remove.pdf

With kind regards,

Dirk Riehle

PS: If the research paper above doesn’t load, please see this copy: http://dirkriehle.com/wp-content/uploads/2016/06/remove.pdf