Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Refactoring in Java

You're reading from   Refactoring in Java Improving code design and maintainability for Java developers

Arrow left icon
Product type Paperback
Published in Dec 2023
Publisher Packt
ISBN-13 9781805126638
Length 292 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Stefano Violetta Stefano Violetta
Author Profile Icon Stefano Violetta
Stefano Violetta
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Part 1: Introduction to Refactoring
2. Chapter 1: What is Refactoring? 3. Chapter 2: Good Coding Habits 4. Part 2: Essence of Refactoring and Good Code
5. Chapter 3: Code Smells 6. Chapter 4: Testing 7. Chapter 5: Refactoring Techniques 8. Chapter 6: Metaprogramming 9. Chapter 7: Static and Dynamic Analysis 10. Part 3: Further Learning FREE CHAPTER
11. Chapter 8: Crafting Quality Every Day 12. Chapter 9: Beyond Code – Mastering Software Architecture 13. Index 14. Other Books You May Enjoy

Simplifying conditional logic

For this section, we will also rely on Martin Fowler and try to explain some of the refactorings to what we consider to be the most common problems. The selection is arbitrary and based solely on our experience. For further details, we refer you to the Further reading section.

Returning a special case instead of null

Do not return null. This is a mantra that everyone – even engineers with years of experience – sometimes forgets. There are cases where a method should return a result but cannot: some error in the execution flow; some exceptional cases. Java and many other languages allow returning null, but it’s preferable not to do so for obvious reasons – among them, avoiding a NullPointerException in the caller or forcing it to check every time that the method’s result is not null.

Tip

Tony Hoare introduced Null references in ALGOL W back in 1965 “simply because it was so easy to implement,”...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image