Clean code—understandable, modifiable, and testable code that works—is not exactly a new topic. In fact, the topic has been around for decades. But that doesn’t mean it’s a solved problem. Everybody who has worked on a nontrivial codebase has likely encountered unclean code. Unclean code is bad for business and developers alike, prevents agility, and poses security risks.
Georg Gruetter explains what clean code is, why unclean code is undesirable, the reasons for unclean code, how to recognize unclean code, and what you can do to avoid it.
Georg Gruetter is a social coding evangelist and software development community leader at Robert Bosch GmbH, where he has been leading the InnerSource community within Bosch since 2009. Georg is a passionate software developer with over 30 years of experience. Previously, he worked for Daimler Chrysler as a researcher, the Zurich System House as a software engineer, and Line Information GmbH as a consultant. Georg has created two open source projects, XHSI and stashNotifier. He is an avid recumbent cyclist and stargazer and generally collects way too many hobbies.
Comments on this page are now closed.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org