Ignite: Creative Solutions to Already Solved...
summary
A laundry list of concrete failures and fixes: zipping PII then emailing the password in a second message that defeats security, Adobe Flash training still required, asserts added to satisfy SonarQube then forcing a test to always fail, getters that only return an object if you already have it, hardcoded debug logs that eat half a gig per build, semicolons that annoy, exceptions constructed but never thrown, business logic buried in catch blocks, and Gradle files edited in Microsoft Word.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:00Trust us. It is safe.
- 1:45Adding assert for sonar
- 3:15Guess which branch this is
- 3:30Documentation is important
- 4:30null checks
- 5:00In case the values ever change
related talks
27mDeveloper Experience: It’s Time to Start Complaining
41mIgnite Sessions
52mEscaping Developer Nightmares
50mAppSec is Too Hard!?
31mStrengthen Our Developer eXperience to Face Obsolescence and View...
13mStandard Classification: Back to Basics: Looking for subtle bugs in beginne...
06mIgnite: Programming your infrastructure
40mAssuring top-notch code quality in the Java Universe