It depends on the codebase and the person I suppose. In my personal projects, I prefer greenfield programming, because I can write code embracing modern C++ fe

It depends on the codebase and the person I suppose. In my personal projects, I prefer greenfield programming, because I can write code embracing modern C++ features that ensure correctness by construction. At work I'm saddled with C#'s shitty ecosystem that doesn't play well with its shitty async stack, and generations of old C++ paradigms that precludes things like constexpr, const correctness, static_assert, we use COM smart pointers instead of shared_ptr, (with no weak_ptr equivalent) shitty naming conventions where variable names are only a repeat of the type, etc. My greenfield work code at work is basically guaranteed to be buggy. I ain't that smart yo. At work, I enjoy fixing bugs. I get to challenge the assumptions of Microsoft and the juggernauts of my corporation's OG Architects. And I get to win. I fight the man and I win. This afternoon I pointed out a bug in code written by a programmer who's been with the company for 20 years. He's the dev lead over a 70 person team. A weeks ago I fixed a bug in our software's core architecture which has been touched by many of the important people in our org. At home I wear sweat pants. At work I wear a cape. Fixing bugs is awesome.