I've been thinking about documenting the development of a game from start to finish like this. Two things I don't like about the way he went about it:
1) Java
2) Time lapse video
It would be a lot more informative to the audience to just blog it or something, posting the code at regular intervals. A video of gameplay now and then is fine, but you wouldn't really need it because readers could just download the code and run it.
Hello /prog/, it's tryouts for the /prog/ Etiquette Advisory Board for the Protection and Preservation of Memes and Contributed Code. The /p/EABPPMCC aims to prevent shitposting in a very real way, by calmly informing the poster where they have gone wrong.
To apply for the /p/EABPPMCC, post using your Advisorcode (Your tripcode while on active duty as a /prog/ Etiquette Advisor) and give examples of at least 5 polite corrections to new users. Only posts using your Advisorcode count.
Fuck this letter. This is the shittiest character in the world. People who open their posts with it deserve to die.
This horrible letter doesn't merely mean that the post is devoid of any form of kality, it also means that your post is actively trying to skuander my precious time.
It's ironic that the /prog/ Etiquette Advisor is what's turning each and every thread that had even the slightest potential of becoming interesting into feces.
Name:
Anonymous2010-08-24 15:23
>>18
Please fuck off and die when trying to FAGiqutte up /prog/