https://doi.org/10.2478/popets-2020-0029

https://doi.org/10.1007/s10664-019-09685-x

https://doi.org/10.1002/spe.2984

• 10.1109/TSE.2021.3106247
• 10.1109/TSE.2021.3100858
• 10.1109/TSE.2021.3094171
• 10.1109/TSE.2021.3087087
• 10.1109/TSE.2020.2964660
• 10.1109/TSE.2021.3135465
• 10.1109/TSE.2021.3129889
• 10.1109/TSE.2021.3128356
• 10.1109/TSE.2021.3125203

https://doi.org/10.1109/icsme46990.2020.00016

https://doi.org/10.1145/3408897

https://doi.org/10.1109/msr52588.2021.00085

https://doi.org/10.1145/3368089.3409705

https://doi.org/10.1109/tse.2019.2910856

https://dl.acm.org/citation.cfm?id=3104029

https://doi.org/10.1109/icse43902.2021.00093

https://doi.org/10.1145/3426422.3426981

• zampetti-2020-continuous-integration-bad-practices.pdf
• yasmin-2020-rest-deprecation.pdf
• wang-2020-regular-expression-bugs.pdf
• masood-2020-agile-teams-self-assignment.pdf
• tamburri-2020-sourceforge-history.pdf
• tamburri-2020-organizational-structure-agile-teams.pdf
• spadini-2020-primers-reminders.pdf
• shrestha-2020-cross-language-interference.pdf
• rodriguez-perez-2020-bugs-born.pdf
• rigger-2020-finding-database-bugs.pdf
• rahman-2020-infrastructure-as-code-defect-taxonomy.pdf
• overney-2020-open-source-donations.pdf
• oliveira-2020-code-commit-metrics-productivity.pdf
• mokhov-2020-build-systems.pdf
• louis-2020-predicting-comment-locations.pdf
• levy-2020-intimate-threats.pdf
• krueger-2020-fmri-code-prose.pdf
• kochhar-2020-from-closed-to-open-source.pdf
• zieris-2020-pair-programming-dynamics.pdf
• wessel-2020-code-review-bots.pdf
• tan-2020-good-first-issues.pdf
• shao-2020-db-perf-antipatterns.pdf
• rahman-2020-irreproducible-bugs.pdf
• chattopadhyay-2020-cognitive-biases-software-development.pdf
• gao-2020-api-learning-processes.pdf
• durieux-2020-restarted-flaky-travis-builds.pdf
• brown-2020-impact-github-suggestions.pdf
• behroozi-2020-debugging-hiring.pdf
• ali-2020-python-survival-analysis.pdf

https://doi.org/10.1109/tse.2019.2918536

on the homepage, when viewing on a smaller screen, long urls break out of the viewport.

Need to add some css (word-wrap: break-word;)

Does the site have any sort of analytics associated with it? I didn't notice anything when poking about in the code. If not, something like google analytics could be added to give visibility of how many people are viewing the site, and which are the most popular articles etc.

https://doi.org/10.1109/icse43902.2021.00031

https://doi.org/10.1016/j.jss.2021.111035

https://doi.org/10.1002/spe.2874

The article summary text does not wrap to the available viewing area, i.e. it is not responsive. Making this text responsive would improve the mobile reading experience

https://doi.org/10.1145/3447245

• stol-2019-abc-research.pdf
• spadini-2019-test-driven-code-review.pdf
• sarker-2019-developer-stress.pdf
• qiu-2019-open-source-social-capital.pdf
• prana-2019-categorizing-readme.pdf
• mitropoulos-2019-javascript-evolution.pdf
• may-2019-stack-overflow-gender-differences.pdf
• malik-2019-backscatter-comparison.pdf
• majumder-2019-hero-developers.pdf
• meyer-2019-work-life-developers.pdf
• johnson-2019-work-environments.pdf
• becker-2019-error-messages.pdf
• barke-2019-role-clarity-agile-teams.pdf
• liang-2019-explain-patch.pdf
• leitao-2019-technology-facilitated-abuse.pdf
• kavaler-2019-javascript-tool-adoption.pdf
• johnson-2019-readability.pdf
• hayashi-2019-daylight-savings-developers.pdf
• hata-2019-source-code-links.pdf
• ford-2019-programmers-look-at-pull-requests.pdf
• dmeiri-2019-bugswarm-dataset.pdf
• de-oliveira-neto-2019-software-engineering-statistical-analysis-evolution.pdf
• catolino-2019-gender-diversity-software-teams.pdf
• blackwell-2019-50-years-psych-programming.pdf
• behroozi-2019-hiring-is-broken.pdf
• bafatakis-2019-python-style.pdf
• aghajani-2019-software-documentation.pdf

• https://rashina.com/stgt/
• https://arxiv.org/abs/2108.09905
• https://www.biorxiv.org/content/10.1101/092205v3.abstract
• https://dl.acm.org/doi/10.1145/3468264.3468592
• 10.1109/TSE.2019.2938525
• https://dl.acm.org/doi/10.1145/3468504
• https://dl.acm.org/doi/10.1145/3469888
• https://doi.org/10.1007/s10664-020-09818-7
• https://link.springer.com/article/10.1007/s10664-021-09995-z
• https://link.springer.com/article/10.1007/s10664-021-10007-3
• https://link.springer.com/article/10.1007/s10664-021-10016-2
• https://link.springer.com/article/10.1007/s10664-021-10025-1
• https://www.win.tue.nl/~aserebre/SANER2020Nathan.pdf
• 0.1177/0735633117707312

https://doi.org/10.1109/icse43902.2021.00095

In a byline such as "Posted Jul 24, 2013 by Fayola Peters...", the author's name should optionally include a link to the author's website.

https://doi.org/10.1109/icse-seip52600.2021.00013

• patra-2021-semantic-bug-seeding.pdf
• zhu-2021-developers-fix-own-simple-bugs.pdf
• zhang-2021-stack-overflow-not-enough.pdf
• sharma-2021-open-source-rationale.pdf
• peitek-2021-code-comprehension-fmri.pdf
• moldon-2021-gamification-effects-software-dev.pdf
• miller-2021-fuzz-testing.pdf
• latendresse-2021-ci-single-statement-bugs.pdf
• kinsman-2021-github-actions.pdf
• kamienski-2021-single-statement-python-bugs.pdf
• jolak-2021-open-textual-vs-graphical.pdf
• hora-2021-test-coverage-exclusion.pdf
• hora-2021-googling-for-development.pdf
• gerosa-2021-open-source-motivation.pdf
• dias-2021-open-source-maintainer.pdf
• chinthanet-2021-good-node-package.pdf
• soares-2021-pr-lifetimes.pdf
• oh-2021-fixing-broken-linux-config.pdf
• golubev-2021-software-refactoring-survey.pdf
• foundjem-2021-release-synchronization.pdf
• baltes-2021-portrayal-of-older-software-developers.pdf

https://doi.org/10.1109/icse43902.2021.00057

https://doi.org/10.1109/icse-seis52602.2021.00011

• brown-2018-blackbox-retrospective.pdf
• tomasdottir-2018-javascript-linters.pdf
• nielebock-2018-commenting.pdf
• reyes-2018-statistical-errors-software-engineering.pdf
• palomba-2018-community-smells-code-smells.pdf
• malloy-2018-python-2-3.pdf
• maenpaa-2018-organizing-for-openness.pdf
• kosar-2018-dsl-comprehension.pdf
• ghiotto-2018-merge-conflicts.pdf
• fucci-2018-need-for-sleep.pdf
• balali-2018-newcomers-barriers.pdf
• ames-2018-logo-critical-history.pdf
• ajami-2018-code-complexity.pdf
• abad-2018-task-interruptions-software-projects.pdf

https://doi.org/10.1016/j.ijhcs.2019.06.009

This issue is a test.

https://doi.org/10.1109/tse.2021.3106280

https://doi.org/10.1007/s10664-021-09983-3

https://doi.org/10.1145/3430665.3456362

https://doi.org/10.1109/tse.2018.2883603

https://doi.org/10.1145/3320269.3384745

https://doi.org/10.1109/icsme46990.2020.00063

https://doi.org/10.1109/msr52588.2021.00062

https://doi.org/10.7717/peerj-cs.241

Make sure the Zoom link in the event page is correct before April 27.

https://doi.org/10.1109/tse.2019.2919305

https://doi.org/10.1109/tse.2019.2928293

https://doi.org/10.1007/s10664-020-09835-6

Coming from a professional software developer perspective my interest in this site is from the point of view of wanting to know what evidence there is for certain practices, i.e. Code Reviews, TDD etc.. I'd like to see something similar to the way the book Making Software presented the information. For example, if I'm interested in TDD, I'd like to go to a page where there is a summary of the evidence / literature for this, along with the links to the articles. The new Category view goes someway to adding in this functionality, but still requires someone to read all the individual articles.

The would probably apply more to certain categories than to others, so I'd propose making changes to the Jekyll templates to allow some of the categories to have their own pages, whereas others would just link to the existing categories page. I'd also like to see a drop down menu in the navigation with links to these category summary pages.

https://doi.org/10.1109/tse.2019.2937025

• weintrop-2017-comparing-blocks.pdf
• tregubov-2017-task-switching.pdf
• tourani-2017-codes-of-conduct.pdf
• sedano-2017-software-development-waste.pdf
• barik-2017-error-messages-eye-tracking.pdf
• alencar-da-costa-2017-rapid-release-integration-delays.pdf
• gao-2017-type-study.pdf
• ford-2017-software-engineer-personas.pdf
• fagerholm-2017-using-ese-in-teaching.pdf
• campos-2017-common-bug-fix-patterns.pdf
• borle-2017-tdd.pdf
• almeida-2017-licensing.pdf
• abdalkareem-2017-trivial-packages.pdf

https://doi.org/10.1109/tse.2019.2918315