I had never experienced the term Ghetto Testing until I read a blog post about how the FarmVille creators use it. One of the biggest parts of Ghetto Testing is to track interest and support for a new feature before actually building it. This means that before a single line of code is written, they throw up a link within the game that allows for people to sign up to be a part of that feature as soon as it become available. This is their way of testing interest. If enough people click on the feature, they will actually build it. If it is something that most people could care less about, they will go on to their next idea. This seems to be entirely different than everything I currently do. Essentially, I create learning objects before anyone has said that they want them. I create courses that people have said that they want but that they are not intimately involved in developing. I produce blog posts that do not have a specific audience, and there is surely no way that I have of asking others for which direction I should be going in. Certainly, I get feedback in comments, but that is only after I have written out my first version. So, this idea of Ghetto testing has really got me thinking about just how few iterations we really get as teachers or as workers. As teachers, at most we get to teach a single topic 4 distinct times a year (within a given unit of study), and most likely, we probably only get to teach it once or twice. The ability for a single lesson to be tested …
Video Rating: 5 / 5