What would the end of the year be without an year-end recap of all the special moments that brought our friends and family at GeoClique together through thick and thin? Well, it would probably be a pretty quiet end of year, huh? And what better way to sum up the year than by taking a look back at all the stuff we #blamechallgren on?
You might be asking yourself “Who exactly is Challgren anyway?” to which we’d fire back a question ourselves, “What rock have you been living under?” In all seriousness, Challgren is our very own co-founder, Chris Hallgren, the true lifeblood of our humble little site. Chris manages the servers on top of his already daunting tasks of maintaining the website and dealing with tech support in the data center. How he does that without losing his mind is being me. And so we joking and lovingly dedicate our posts to blaming the guy when things go wrong, all to lighten the mood and to let him know that we all understand the difficulties that come with managing so many aspects about our social network.
Without further ado, let’s take a look at some of the things that we’ve blamed on Chris over the past year, shall we? These posts are by no means in chronological order, and may have happened prior to 2013. For the sake of this article, we wanted to cover a variety of bases, so my apologies to any that were shared in private.
We blamed Challgren for our own poor health and misfortunes
We blamed Challgren for random silliness and missed opportunities
We blamed Challgren on our technology issues
Sometimes, we don’t even need a reason to blame Challgren
Challgren takes is all in stride, blames himself for stuff
So what about the stuff we fixed? Do we stop blaming Challgren now?
(Answer: Nope, carry on as usual…)
So there you have it, a quick recap of some of the random stuff that we like to #blamechallgren with. You can see how easy it is to do. Next time you’re on the site and feeling like someone is to blame for your mood, well… you know what to do.