Code this, not that: Exposing, squashing, and preventing bugs

In this session, we'll look at several tricks, techniques, practices, and tools for keeping bugs out of your code. We'll look at investigative tools that uncover the places where bugs breed. We'll see how to write our code differently so that those bugs won't have a place to thrive. And we'll see how to work preventative measures into project builds to keep those bugs from infesting our code in the first place.

Every line of code that you write is a potential software bug. It's not intentional, but it's true. Whenever you put your fingers to the keyboard and start banging out what you think is a brilliant software solution, there's a good chance you've just introduced a few defects to your project.

Some software defects are obvious and readily present themselves. Those are the ones you squash before QA even sees them. Others are a bit sneaky, but can usually be rooted out by a solid testing effort. But then there are those bugs that are so dastardly that they only present themselves in a production runtime, appearing just long enough to terrify (or at least annoy) users, before slithering back into hiding making it difficult to eradicate them.

Wouldn't it be great if you could expose those bugs before they creep out into your production deployment?

About Craig Walls

Craig Walls is a Principal Engineer, Java Champion, Alexa Champion, and the author of Spring AI in Action, Spring in Action, and Build Talking Apps. He's a zealous promoter of the Spring Framework, speaking frequently at local user groups and conferences and writing about Spring. When he's not slinging code, Craig is planning his next trip to Disney World or Disneyland and spending as much time as he can with his wife, two daughters, 1 bird and 2 dogs.

More About Craig »