In the game development context, what is the best kind of information that a blog can share?
Explaining story (narrative) requires caution because you don't want to give the story away, or try to explain the way your mind thinks. It seems to go against the purpose of storytelling.
Sharing technical information is useful for documentation, useful for deliberating, useful for future planning, useful for making you look smart. Documentation, however, if best handled internally where the data/info is better managed than a CMS.
Experiences can be shared, but what kind of experience do you get from sitting in front of a computer all day? And if I'd be honest, that's mostly what game devs do. Fancy going out for a photography session to capture textures or taking a video of someone taking a walk for reference. Everything's online anyway.
Game developers taking a piss at game development seem like a good pastime if we go by the popularity of these types of things. I'm not qualified, however, because I've not really worked professional in game dev before. Also going along with the gaming news crowd is a bit like taking a second serving of vomit. A bit boring if not nauseating. To be fair, I like reading the game dev day-to-day experiences, but that's for consumption, not for dishing out.
But until that comes to pass, what do I blog about?
Well, at the end of the day, no one's reading, right? I can say anything. Isn't that what this is about?
Watch out! Here I come!
No comments:
Post a Comment