Readin, ritin, and refactoring
Code should be written to be read…alas it often isn't. When you inherit someone else's mess, what do you do? This talk will discuss what can be done to handle this all too typical situations. We'll see how tests and code coverage metrics along with other indicators can help us see shapes in the fog.
Code should be written to be read…alas it often isn't. When you inherit someone else's mess, what do you do? This talk will discuss what can be done to handle this all too typical situations. We'll see how tests and code coverage metrics along with other indicators can help us see shapes in the fog.
About Nathaniel Schutta
Nathaniel T. Schutta is a software architect and Java Champion focused on cloud computing, developer happiness and building usable applications. A proponent of polyglot programming, Nate has written multiple books, appeared in countless videos and many podcasts. He’s also a seasoned speaker who regularly presents at worldwide conferences, No Fluff Just Stuff symposia, meetups, universities, and user groups. In addition to his day job, Nate is an adjunct professor at the University of Minnesota, where he teaches students to embrace (and evaluate) technical change. Driven to rid the world of bad presentations, he coauthored the book Presentation Patterns with Neal Ford and Matthew McCullough, and he also published Thinking Architecturally and Responsible Microservices available from O’Reilly. His latest book, Fundamentals of Software Engineering, is currently available in early release.
More About Nathaniel »