📢 ESEM 2026 – Software Engineering in Practice (SEIP) Track

A forum for practitioners & researchers to share real-world experiences with SE processes, methods, and tools. Submissions are evaluated for relevance and practical impact.

📝 Abstract: 20 May 2026
📄 Paper: 27 May 2026
📬 Notification: 8 July 2026
📦 Camera-ready: 5 Aug 2026

🔗 https://conf.researchr.org/track/eseiw-2026/eseiw-2026-esem---seip-track

#ESEM2026 #EmpiricalSoftwareEngineering #CFP

📢 Update for ESEM 2026 authors

Starting this year, ESEM introduces a new publication model with DAGSTUHL LIPIcs proceedings.

This change aims to improve openness, accessibility, and long-term availability of research results.

If you are planning to submit, please check the FAQ for details on the new process.

🔗 https://conf.researchr.org/info/eseiw-2026/dagstuhl-lipics---faq-for-authors

#ESEM2026 #EmpiricalSoftwareEngineering

Dagstuhl LIPIcs - FAQ for Authors - ESEIW 2026

Welcome to the joint website of ESEIW 2026, the Empirical Software Engineering International Week 2026, and ESEM 2026, the 20th International Symposium on Empirical Software Engineering and Measurement.

📢 ESEM 2026 – Emerging Results, Vision & Reflection Papers Track

Share early ideas, future visions, or reflections on influential studies in empirical software engineering.

📝 Abstract: 22 May 2026
📄 Paper: 29 May 2026
📬 Notification: 10 July 2026
📦 Camera-ready: 5 Aug 2026

More details: https://conf.researchr.org/track/eseiw-2026/eseiw-2026-emerging-results-and-vision-track

#ESEM2026 #EmpiricalSoftwareEngineering #CFP

Reposting with updated graphic.

📢 ESEM 2026 – Registered Reports Track

The RR track supports rigorous empirical software engineering research by reviewing study motivation, design, and planned analyses before data collection.

📝 Initial report: 13 April 2026
📋 PC reviews available: 4 May 2026
✏️ Author response : 18 May 2026
📬 Stage 1 notification: 8 June 2026
📄 arXiv submission (mandatory): 13 July 2026

More details: https://conf.researchr.org/track/eseiw-2026/eseiw-2026-esem---registered-reports-track

#ESEM2026 #EmpiricalSoftwareEngineering #CFP

Reposting with updated graphic.

📢 ESEM 2026 – Technical Track (Munich, 4–9 Oct 2026 🇩🇪)

We invite high-quality empirical research on software engineering and measurement.

📝 Abstract (mandatory): 22 April 2026
📄 Paper submission: 29 April 2026
💬 Author clarification (optional): 16–23 June 2026
📬 Notification: 30 June 2026
📦 Camera-ready: 5 August 2026

More details: https://conf.researchr.org/track/eseiw-2026/eseiw-2026-esem---technical-track

#ESEM2026 #EmpiricalSoftwareEngineering #CFP

Munich, October 2026 🇩🇪

ESEIW 2026 & ESEM 2026 are coming — and submission preparation should start now!

Full papers, emerging results and vision papers, registered reports, industry papers, journal-first, doctoral symposium — detailed track info is available on the joint website.

Don’t miss the first deadlines 🎯

🔗 https://conf.researchr.org/home/eseiw-2026

#ESEIW2026 #ESEM2026 #EmpiricalSoftwareEngineering

ESEIW 2026

Welcome to the joint website of ESEIW 2026, the Empirical Software Engineering International Week 2026, and ESEM 2026, the 20th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement. Note: Information on the events of the week, the ESEM-related tracks and their deadlines will be published very soon.

This is the official Mastodon account of the International Symposium on Empirical Software Engineering and Measurement (ESEM) and Empirical Software Engineering International Week (ESEIW).

We’re excited to join the Mastodon community and look forward to connecting with researchers, practitioners, and friends from around the world.

Stay tuned for CFP announcements, deadlines, and conference updates!

#ESEM #ESEIW #ESEM2026 #EmpiricalSoftwareEngineering

#introductions I'm Stephan, originally an English Philologist and Linguist, now a #SoftwareEngineering researcher at the German Aerospace Center's (https://social.bund.de/@dlr) Institute of Software Technology in #Berlin.

I'm a 2018 Fellow of the Software Sustainability Institute (https://mastodon.social/@SoftwareSaved), founder and lead of the #CitationFileFormat (https://citation-file-format.github.io/) and co-founder of de-RSE (https://mastodon.social/@de_rse).

I work on #ResearchSoftware, #SoftwareCitation, #SoftwarePublication, #SoftwareIntelligence, #SoftwareSustainability, #EmpiricalSoftwareEngineering.

DLR (@[email protected])

554 Posts, 154 Following, 4.89K Followers · Wir sind das Deutsche Zentrum für Luft- und Raumfahrt (DLR) und lieben unsere Themen Luftfahrt, Raumfahrt, Energie, Verkehr, Digitalisierung & Sicherheit! 
Web: https://www.dlr.de/de
Impressum: https://www.dlr.de/de/service/impressum 
Datenschutz: https://www.dlr.de/de/service/datenschutz 
Netiquette: https://www.dlr.de/de/aktuelles/social-media/netiquette

social.bund.de
I am happy and honored to announce that I have joined the editorial board of the Empirical Software Engineering journal, one of the best and most highly cited journals in our field. I am looking forward to your submissions!
https://link.springer.com/journal/10664
@seresearchers
#EmpiricalSoftwareEngineering
Empirical Software Engineering

Empirical Software Engineering serves as a vital forum for applied software engineering research with a strong empirical focus. A platform for empirical ...

SpringerLink

“Larger pull requests lead to longer delays which lead to more time to make changes which leads to larger pull requests.”

Claim by @kentbeck that can be empirically tested with repository mining research. Not aware of papers that look at such reinforcement loops.

https://tidyfirst.substack.com/p/thinking-about-code-review

@seresearchers #codereview #PullRequests #MiningSoftwareRepositories #EmpiricalSoftwareEngineering

Thinking About Code Review

Think about your team workflow. Then try what makes sense for your context. Then adjust. The most exciting words in engineering are, “It turns out…”. A recent Twitter kerfuffle about the pull request team workflow happened to mention me. The last thing I want to do is to participate in another pissing contest about code reviews, but here I am.

Software Design: Tidy First?