Peer-reviewed papers, registered reports, and empirical studies of how software is really built.
This is where the peer-reviewed work lives. Most of it sits at the intersection of empirical software engineering and continuous integration: how teams decide to adopt CI, why a quarter of those adoptions are later abandoned, and what a recommendation system would have to understand about a project before it could give useful advice. Each post summarises a paper in plain language, states the central argument, and links to the full text. If you are looking for the formal versions, the venue and paper link are attached to every entry.