As some of you may have heard by now, Dale North (our editor in chief from 2010-2014) will be moving on to sunnier, though less 'toidy skies. You can read that announcement here. It's no secret that Dale and I have definitely punched each other in the dick over the years, but in the end we're still friends. No drama. Please do wish Dale all the best, as he leaves us with our highest praises and recommendations. As the once leader of one of the biggest independent gaming bordellos Mr. North leaves tough seat to fill, covered in corgi hair.
As we transition to the next chapter of Destructoid (expect big changes around here -- namely we're going back to being weird) I will be returning as full-time bossman before appointing a new editor. Yes, I will be hiring sometime in Q4 to lend me a hand in running the house of the robot, so if you're interested polish up those resumes, dump your girlfriends, and so on. Our new editor in chief will likely be hired from within, but I'm also looking to discover some new blood to usher in our 9TH YEAR (OMG) of bloggy existence.
Where are they now?
Saying goodbye to the people I loved working with is the worst thing, by far, I must do as Destructoid's publisher. Fortunately, most of them stay in the industry and we end up working together again anyway... and by "working" I mostly mean getting piss drunk at gaming event after-parties. #omgcollusion
This video, which I presented at a PAX panel in 2012, was to demonstrate that some of our ex-editors -- ALL of which were regular community members just like you -- were able to secure great positions in different parts of the industry with almost no prior experience other than their passion for gaming and their tenacity to blog.
Is this what you wish, deep down in your heart, for your career to lead you?
Then get blogging, ladies.
Webmaster Dojo is an editorial column about my experiences in running a videogame site. If you enjoy this sort of diatribe, please suggest a topic for my next article in our super-cool new comments system below.
can cause it. You can fix it by adding *.disqus.com to your whitelists.