Technical Practices: No Enums

Quality-wise of this post; not gonna lie - Probably will be low. It's 7am and I'm low on posts. This isn't a bubbling pressing issue on my mind. I don't need to stream my thoughts to work through something... What I do need... is a post for this week. Soooo.…

Beneficial Results - Simpler Code

Simpler code. Don't we all wish the code we deal with could be simple? Simple is hard. Simple is challenging. Simple is complex. A short letter is much harder to write than a long one. Why do you think my blog posts are so damn wordy? I don't put in…

Tool Impact On Developer Discipline - Frameworks

There's a lot of tools that exist to make what developers to easier to do. If it's something we do a lot, we tend to find ways to have something do it for us. I've done it. I'll probably do it again. I built a little tool to automate the…

Refactoring: Where to start

I've had a lot of discussions around applying the MicroObject technical practices to legacy code. "These practices are clearly great for new code, but how can we work them into our existing code?" Even if it's not your definition of legacy code; it can probably be refactored -…

Thoughts: Testing Without Mocks

James Shore has a post, Testing Without Mocks, that I've recently been introduced to. Skimming through the introduction of the post, it looks like the goals of this align well with what MicroObjects give us in terms of testability. I'm going to go through the article and post my thoughts…

Technical Practice: Objects avoid Primitive Obsession

I have a GitHub project FluentTypes which I've written about before. The goal is to avoid the problems of Primitive Obsession. We want to represent what we're thinking. After working in MicroObjects style and using the style represented by the Fluent Types; I found a new way. To my credit,…

Refactoring Legacy Code: Remove future proofing

The legacy code I'm playing with at work had some nice future proofing. It wasn't quite big design up front, but it was some future proofing. I got some out, but there's still a whole level of abstraction that's pending removal. I'm not here to write about what I haven't…

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 I did…

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 the definitions of "Legacy Code&…