I don’t know if I’ll ever get used to the cadence of four-day holiday work weeks. There’s five or so of them each year and every time they come around it feels strange. With Monday being President’s Day, a national holiday, a lot of people got a quick four-day work week. Don’t get me wrong, I enjoy getting Mondays off, but these four-day weeks just have a different vibe. Maybe I’ll get used to them by the time I retire.
I spent a lot of time this week reading Working Effectively with Legacy Code. I’m learning a lot by going through it. A lot of the ideas I’ve read about so far seem to be natural practices. Things like sprout method/class and wrap method/class beautifully summarized techniques that I’ve aimed to use when editing legacy code. My guess is that these ideas have spread throughout the development community to the point of ubiquity. These ideas have spread so far that they seem natural at this point.
Pluralsight Course(s): Functional-Lite Programming
Book(s): C# 7.0 in a Nutshell
Pluralsight Course(s): Securing ASP.NET Core with OAuth2 and OpenID Connect, React 16 - The Complete Guide
Book(s): Working Effectively with Legacy Code
On the Next…
I want to complete Working Effectively with Legacy Code this week. I’m halfway through it now and I think I should be able to finish it by the end of the week. So far, it really seems like Interfaces are the MVP when working with legacy code. Making the code we need to change implement an interface allows us to more easily get that code under test. Code under test is far superior to code that isn’t under test. Over time, by repeatedly making small changes and getting more code under test, a legacy codebase can start to improve.