Skip To Main Content
Jacek Czerwonka on Muck Rack

Jacek Czerwonka

As seen in: arXiv
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work. Claim your profile
Back to Jacek Czerwonka’s profile

Articles by Jacek Czerwonka

[2306.08980] The Upper Bound of Information Diffusion in Code Review

|
By Daniel Mendez, Krzysztof Wnuk, Ehsan Zabardast, Jacek Czerwonka
| arXiv
[Submitted on 15 Jun 2023 ( v1 ), last revised 11 Jul 2024 (this version, v4)] Title:The Upper Bound of Information Diffusion in Code Review View a PDF of the paper titled The Upper Bound of Information Diffusion in Code Review, by Michael Dorner and Daniel Mendez and Krzysztof Wnuk and Ehsan Zabardast and Jacek Czerwonka View PDF Abstract:Background: Code review, the discussion around a code change among humans, forms a communication network that enables its participants to exchange and...
Open in Who Shared Issue with article?

CodeFlow: Improving the Code Review Process at Microsoft

|
By Jacek Czerwonka, Christian Bird, Terry Coatta, Michaela Greiler, Lucas Panjer
| ACM - Association for Computing Machinery
The September/October issue of acmqueue is out now Subscribers and ACM Professional members login here PDF November 13, 2018 Volume 16, issue 5 CodeFlow: Improving the Code Review Process at Microsoft A discussion with Jacek Czerwonka, Michaela Greiler, Christian Bird, Lucas Panjer, and Terry Coatta You may be wondering, "Code review process? Isn't that obvious?" But code reviews are pervasive. Any developer is likely to be asked at any time to review someone else's code.
Open in Who Shared Issue with article?

Code reviews are not (primarily) for finding bugs | Visual Studio

|
By Jacek Czerwonka
| visualstudio.com
Peer code reviews are a standard practice in software engineering. Open source workflows especially are designed to enforce a successful peer review before the merge of a change into the main codebase. Who reviews code and accepts or blocks the change from becoming a part of the codebase is crucially important. The process of code reviewing in software engineering is similar to a plan review in civil engineering or a paper review in academia.
Open in Who Shared Issue with article?
Show More