A Java Refactoring Story
‘Entropy is the price of a Structure ‘. But sometimes, the price turns too high to pay. Is your Java codebase turning untestable, unreadable, and unmaintainable? Does your costs to add new features aren’t meeting the ROI?
‘Entropy is the price of a Structure ‘. But sometimes, the price turns too high to pay. Is your Java codebase turning untestable, unreadable, and unmaintainable? Does your costs to add new features aren’t meeting the ROI?
This live hacking session will refactor a small Java Sudoku Brute-Force Solver. The code is anything but bad, but its age shows. In short sessions we want to give the legacy Java code a rejuvenating treatment. You will discover a personal approach on how to perform refactoring on untested Java …
A new sprint starts and you have to implement a new feature, you naively open the file where the functionality ought to live. To your great horror, a five headed monster seats there scaring the hell out of any developer trying to change that file. You know the time has …
Java has turned 20, but we still haven’t figured out how to create great Java code. Of course, we have examples of great developers and great code, but shouldn’t it be something common rather than unusual? We’ve seen Domain-Driven Design, Effective Java, Clean Code, Refactoring, Design Patterns….
This talk will provide a quick introduction to Docker images (build time), containers (run time), and registry (distribution). It shows how to take an existing Java EE application and package it as a monolithic application as a single Docker image. The application will then be refactored in to multiple microservices …
When a Java code-base grows beyond a certain size, any original arrangement of source files (or software architecture) is often lost. The developers also become lost, and start drowning in the ever-expanding sea of classes. Usually the underlying code – the classes – are in reasonable shape. The problem is …