The ideal code. Fiction or reality
summary
Defines an actionable checklist: readable, compact, reliable, self‑explaining code with separation of commands vs queries; measures tradeoffs with concrete tools — uses JMH benchmarks to show plain arrays beat lists/maps for bulk creation while plain objects are nearly as fast for field access; recommends modern APIs like Java 8 streams, java.time, HashMap’s Java‑8 treeify and libraries (Caffeine, Jackson, Apache Commons) instead of ad‑hoc code; shows tests, clear exception messages and static metrics as practical steps toward higher quality.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:36Ideal code as myth
- 4:06Requirements for ideal code
- 8:01Code readability
- 10:10Code compactness
- 12:02Code clarity
- 15:42Code reliability
- 21:56Error messages
- 22:37Tests as documentation
- 23:18Code reuse
- 25:03Code flexibility
- 27:51Code security
- 33:34Code scalability
- 35:19Code efficiency
- 38:11Ideal code reality
- 39:38Q&A
related talks
46mCode Smells - Hall of Fame
40mGood Code: What, Why, and How to Get There
50mThe Art of Clean Code
39mRead my code, or why writing readable code matters
40mAssuring top-notch code quality in the Java Universe
33mThe Catcher in the Code
49mJava's Hidden Gems: Tools and Libraries
50mThe Code is Documentation Enough