Bad code and team performance

A good way to look at bad code is code lacking the technical practices that help other developers understand what it is doing. When we’re coding solo, it doesn’t matter so much. Bad code will just slow you down and feel a little demoralizing at times. It does not affect anybody else. However, most professionals code in development teams, which is a whole different game. Bad code really slows a team down. The following two studies are interesting as far as this is concerned:

Technical Debt Cripples Software Developer Productivity: A longitudinal study on developers’ daily software development work
...

Getting Started

Building the Case for TDD

Using TDD to Create Good Code

Dispelling Common Myths about TDD

Building an Application Using TDD

Writing Our First Test

Following the Rhythms of TDD

Driving Design—TDD and SOLID

Test Doubles—Stubs and Mocks

Hexagonal Architecture—Decoupling External Systems

FIRST Tests and the Test Pyramid

Exploring TDD with Quality Assurance

Test First, Test Later, Test Never

Driving the Domain Layer

Driving the Database Layer

Driving the Web Layer

Wrap Up

Appendix

Decreasing Team Performance

Bad code and team performance