Chesterton's half-implemented fence that he built just in case

Automated excerpt

There's a fun part of starting every new software engineering job as you navigate an unfamiliar codebase: You want to make some changes, maybe refactor some old code, and you see some things that strike you as odd. You ask the engineers who you think might have some context, but they're not sure why it was written that way either. Chesterton's fence There is a parable by G. Understand why the process was originally instituted. Make sure to explain the purpose of the fence when you build it.

Selected automatically from source text; not independently written or fact-checked. Read the original for full context.