Utility Classes Are Killing Us
Utility classes are a very convenient tool for sharing commonly used procedures in Java and many other object-oriented languages. There are Apache Commons, Guava, and JDK by itself who ship that utility classes to us, with sometimes hundreds of procedures in them. The question is whether this design is really object-oriented and how much does it help us keep our code clean. Do we really need these procedures in OOP? And if not, what is the alternative? How can we share code between classes in Java?
Yegor is a CTO at Teamed.io, a software development company with an extremely distributed working model; a VC at SeedRamp.com; a regular blogger at www.yegor256.com; author of Elegant Objects book; a proud holder of PMP and OCMEA certifications; a hands-on Java developer and a lead architect of rultor.com and takes.org. Yegor lives in Palo Alto, CA and Kyiv, Ukraine.