Pat Hermens

For a long time, my introductory paragraph has read “…interesting challenges get me out of bed in the morning!”, but it’s been a while since I’ve validated that as a fact.

As 2018 draws to a close (and I get closer to some of the deadlines for my long-term goals), now is as good a time as any to revalidate that I’m happy with that sentiment, and that I’m still doing my best to ensure that it’s still the case…

I thought it might be interesting to outline where my latest GitHub project fgitvis came from and what my intent is to make it easy for other people to contribute.

I thought it might be interesting to type up what I do to prepare for an event like the “Behind the Scenes” at Coolblue - to get you truly “behind the scenes” of the “Behind the Scenes” if you will.

As I wrote in my last post, I’m a big fan of clean, clear, simple unit-tests. Part of this involves figuring out where your “boundary” is and clarifying the limits of the code that you’re responsible for. Normally this is simple and straightforward, but ~sometimes~most of the time, trying to test a class with an unnecessary access modifier and limited construction options is going to end in frustration.

I’m a big fan of unit-testing. I especially like unit testing that is simple, clean and easy to follow. It gives me a good feeling that the rest of the code that is behind the tests is easy to understand and easy to maintain, and whilst this isn’t always true, from my experience, it’s pretty close.