A little over a year ago, I wrote a post about switching from WordPress to Jekyll. There were a number of reasons for switching including faster load time, no database connections and handy CLI build tools. However, what seemed like a manageable transition that would give me experience with a new platform turned into a roadblock for writing content. In fact, I’ve only written one post since then and although I can’t blame this completely on switching to a new platform, it is certainly a contributing factor.

The moral of the story is this – if something works well, don’t scrap it and try something completely different. My experience as it pertains to this situation is that it leads to a less productive workflow, especially where the new solution has a relatively steep learning curve. There are always going to be ares of improvement, but it’s best to focus on those and address them on an individual level as opposed to seeing the whole system as a problem and looking to replace it. You might say this seems like common sense and in retrospect I completely agree, but it’s a trap that can be easy to fall for in the hope that it will solve all of your problems. No solution is perfect.