Refactoring Legacy Code: Leave Tested Methods Public

When refactoring from a large to small API, use interfaces for the new methods, but leave the old public IFF they are well tested. Its not worth re-working all the tests when they're hidden by using the interface This is a short little post about a small thing…

Refactor Legacy Code: Pass The Bigger Thing

Working in legacy code makes it clear how important refactoring is to maintainability. I'll go so far with the importance of Refactoring to say, "If the code isn't refactored, it isn't maintainable." Clearly I think this is a huge thing. One of…

Refactor Legacy Code: Reduce DataBags

What is a DataBag? I consider a databag any object that primarily acts as transportation for data. In C++, this would be a struct. Ignoring any associated functions, the data's exposed and being passed around. Java would represent a databag by a class with primarily get/set methods…

Antipattern: UI Databinding Android

This is me going through the Android recommendations on how to do databinding. As with A LOT of practices that increase the complexity and harm maintainability; databinding and the recommendations enable, perceived, QUICK development, but it has such a high cost afterwards; there WILL be re-writes. It won't…

Antipattern: UI Databinding

I started this EARLY into my adventures gettign to understand what Object Oriented Programming is. The UI is always a rough part of the experience. I found some effective ways to deal with it. My latest way is to have the UI do nothing [https://quinngil.com/2019/01/08/…

Technical Practice: No Inheritance

I've written before about the technical practice of composition over inheritance [https://quinngil.com/2017/11/26/uobjects-composition-over-inheritance/] but what about the idea that we have NO inheritance? I use inheritance VERY infrequently. I have two cases where I use inheritance. 1. Only when there is clear duplication…

Patterns: Chain of Responsibility

The Chain of Responsibility is one of the major patterns I use in my MicroObject projects. When I have a sequence of events, applying the practices forces things into a very narrow set of forms. I've found one that I feel is the clearest, cleanest, and most inline…

The UI - It Does Nothing!

The UI should have no logic That's not strong enough. THE UI MUST DO NOTHING! That's better. The UI is the edge of our system. The edges of our system are hard to test. They interact with things that are not ours. We don't…