This book is 55% complete
Last updated on 2016-09-17
About the Book
The two bibles that any Java developer should have on their desk are Clean Code and Essential Java. Whilst these are wonderful books, they still have problems. Firstly, they are now showing their age. We’re well into the lifespan of Java 8 and there is still no single resource pointing us to how to write great clean code with the new paradigm that is upon us. Further, particularly with Essential Java, the material is very very dry. You’re never going to remember the 80 or so points in full detail to apply to your code. It’s great as a reference, but there needs to be something else.
Beautiful Java is a strongly opinionated book on what good Java code looks like in the modern day, taken from my years of experience of experience working on enterprise applications. Some of these opinions are not new and will tie in with the general consensus. Others may appear controversial on first site, but I have witnessed over a variety of codebases with a lot of other colleagues how they can directly attribute to a code base that is easy to understand and maintain over a long period of time.
This book is also designed to be easy to read. It is not a book that will dive into the nuances of the JVM and bore you with a million edge cases. It is designed as a clear guide to approaching application design and coding. A good dollop of common sense is required when applying these to your day to day applications.
Thank you for taking the time to read. I am sure you won’t be disappointed.
Part One: Clean Code
Clean code trumps all other requirements and eager optimisation is the enemy
- Measure everything
- Using Java 8? Plese avoid functional vomit
Anatomy of a good Java Test
- Naming Your Test
- Test Code
- Constructor vs Getter; A response and a better way
- A Practical Example:
Java Builders from the Start
- Immutable builders
- Incomplete object protection
- Eager Instantiation is just better
- How to properly use Exceptions in Java
- Immutability in Java
Upgrade your code conventions
- Zero Comments (except on public APIs)
- Don’t start test methods with the word “test”
- Don’t use @Override
- Don’t use get/set
- Working code > Performant code
- Use your own exception type
Using an ApplicationEvents for cleaner, tested code
- Introducing ApplicationEvents
- A concrete example
- A Little further
- In conclusion
Avoid working with Classes and Reflection
- Switch statements/instanceof
- Reflection and Dependency Injection
- Clean code trumps all other requirements and eager optimisation is the enemy
Part Two: Everything else
Does your application need a database?
- So What’s the Alternative?
- Phone a Friend
- None of These Apply to My System!
Using TDD and Progressive Enhancement to build a chat application
- What’s progressive enhancement?
- Applying this to a chat application
- The Keyboard shouldn’t be the bottleneck
The quick way to a Java 8 webserver using Spark
- A slightly more complex example
- TDD: The “D” is for design
- Does your application need a database?
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms...