Improving code style when working on a legacy code base

Published on April 27, 2015 and filed under Software engineering
Written by Hannes Van De Vreken and will take

3 minutes

of your time.

In short

Technical advice: In this blog post I would like to share some thoughts on code style details for cleaner diffs and due dilligence

Want to see more articles like this in your inbox? You know what to do.

Related articles

.Blogposts___StyledBackgroundImage-sc-1eq0cg3-4.huWSDb.gbi--1577437139:before { opacity: 1; background-image: url('/static/6987e9e2ae956e6dc520ea5f572eb682/110cd/blogpost-legacy-greenfield-code-1.png'); }

I'm starting a greenfield project and I'm terrified.

I'm starting a greenfield project and I'm terrified.

Jonas Drieghe

August 04, 2020

.Blogposts___StyledBackgroundImage-sc-1eq0cg3-4.huWSDb.gbi--285458285:before { opacity: 1; background-image: url('/static/5d95783bf038156e5fd8b065bdbd9685/110cd/blog-legacy-code-grandfaterhing.png'); }

Grandfathering in legacy

Grandfathering in legacy

Maarten Scholz

April 16, 2020

.Blogposts___StyledBackgroundImage-sc-1eq0cg3-4.huWSDb.gbi-1720880598:before { opacity: 1; background-image: url('/static/82ca7dbebb4003f900c97e82b88530ca/110cd/blog-refactoring.png'); }

Refactoring towards testability

Refactoring towards testability

Wouter Sioen

August 07, 2018