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 Grütter is a social coding evangelist and developer advocate at Bosch Software Innovations. He cofounded and led the first InnerSource community at Bosch. Georg is a passionate software developer with over 30 years of experience. Previously, he held various positions and roles at Bosch, Line Information, the Zurich System House, and DaimlerChrysler. Georg has created two open source projects, XHSI and stashNotifier. He’s an avid recumbent cyclist and mountain biker who also loves photography and chocolate.
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