InfoQ Homepage Code Reviews Content on InfoQ
Articles
RSS Feed-
/articles/craftleadership-developers-craft-code/en/smallimage/small-1669118526409.jpg)
Craftleadership: Craft Your Leadership as Developers Craft Code
Learning software craftership made me reconsider how I wrote code. Being an experienced software team manager, I try to reevaluate my management practices in the same way: what could test-driven management or pair-management be? Here I propose different insights on how software craftership tools and mindset are transposable to the management domain.
-
/articles/co-creation-patterns-software-development/en/smallimage/logo-1667590759022.jpg)
From Async Code Reviews to Co-Creation Patterns
This article dives into the throughput and quality of the async code review process, which are very important dimensions to optimize for in product development teams. It also explains why co-creation patterns – Pair and Mob programming – as an alternative way of working are able to optimize for both of those dimensions, instead of needing to trade off between them.
-
/articles/software-engineering-google/en/smallimage/software-engineering-google-s-1622200397846.jpg)
Software Engineering at Google: Practices, Tools, Values, and Culture
The book Software Engineering at Google provides insights into the practices and tools used at Google to develop and maintain software with respect to time, scale, and the tradeoffs that all engineers make in development. It also explores the engineering values and the culture that’s based on them, emphasizing the main differences between programming and software engineering.
-
/articles/practices-better-code-reviews/en/smallimage/practices-for-better-code-reviews-logo-small-1573541867238.jpg)
13 Practices for Better Code Reviews
When done incorrectly, code review can be irritating, excessively time consuming, and have little or no impact on code quality. However, if done well, it can improve the quality of code and reduce the overall time spent delivering features. This article provides several good practices regarding both technical and cultural aspects of code review.
-
/articles/book-review-refactoring-second-edition/en/smallimage/refactoring-martin-fowler-s-1547048069753.jpeg)
Q&A on the Book Refactoring - Second Edition
The book Refactoring - Second Edition by Martin Fowler explores how you can improve the design and quality of your code in small steps, without changing external behavior. It consists of around seventy detailed descriptions of refactorings, including a motivation for doing them, the mechanics, and an example.
-
/articles/peer-reviews-sandbag-propel/en/smallimage/Peer-Reviews-logo-1531354656439.jpg)
Peer Reviews Either Sandbag or Propel Agile Development
Agile teams are hungry for feedback, but are they getting it fast enough? If your peer review process isn’t structured right, it could be dragging down your development. This article explains how your team can unlock the full potential of code and document reviews by employing a structured, but flexible process that accelerates development and fosters a culture of collaboration
-
/articles/effective-code-reviews/en/smallimage/agile-logo.jpg)
Ways to Make Code Reviews More Effective
Performing Code Reviews helps to increase code quality, share knowledge and responsibility, and build better software and a better team. However, the big question remains – what is it we should be looking for? There are a lot of different things to consider. This article will list a wide range of items to check, and drill a little deeper into two specific areas: performance and security.
-
/articles/infrastructure-code-reviews/en/smallimage/devops.jpg)
Infrastructure Code Reviews
As infrastructure becomes code, reviewing (and testing) provides the confidence necessary for refactoring and fixing systems. Reviews also help spread consistent best practices throughout an organization and are applicable where testing might require too much scaffolding.
-
/articles/technical-social-history-software/en/smallimage/logo.jpg)
Interview and Book Review of The Technical and Social History of Software Engineering
Capers Jones wrote the book The Technical and Social History of Software Engineering in which he provides an overview of the evolution of information technology and software development. InfoQ interviewed Capers about advancements and events in software engineering and the effects that they have had on our society.
-
/articles/interview-openstack-ci-test-automation/en/smallimage/logo.jpg)
Monty Taylor and Jim Blair on CI and Test Automation at OpenStack
Monty Taylor and James Blair talk about the build and test challenges they face at OpenStack, and how they managed to tackle them. Managing hundreds of VMs on public clouds, integrating up to 400 commits a day and running thousands of test jobs on them are some of the challenges described.