Just In Time Design
We don’t perfect design in our programming until we’re sure we’re going to keep it.
Here is a link to the article from 2003 that impressed me, which I mentioned in the video.
Similar Posts
1,000 Ways Not to Get SPSS Fuzzy to Work
I thought my day today would be easy. There is a FUZZY module that goes with the SPSS integration for Python. All I needed to do was install the SPSS Python Integration technologies, then, maybe install the fuzzy plug in and it would all work. Both the rocket scientist and I worked on this most…
How SAS Helped Me Make Our Best-Selling Educational Game: Part 2
Last time, I gave a bit about the requirements of a game to match the most synonyms in one minute, and how what I learned using SAS was a basis for several parts of the game. This activity is going into Making Camp Premium, which will be a paid version of our best-selling game, Making…
Super-computing doesn’t take super powers: Part I
“How often times it happens that we live our lives in chains, and we never even know we hold the key.” I remember listening to that song by The Eagles at the Mississippi River Fest back when I was a teenager. Yes, the Mississippi River existed back then. It’s a good point. So often we…
SAS Tip of the Day: The _character_ array and fixing all character variables
Contrary to appearances, this is not an abandoned blog. I’ve been super-busy with 7 Generation Games, where we released two new games and a customized app for a client this month! At the same time, I’m in Santiago, Chile piloting games for our Spanish language brand, Strong Mind Studios, you can read some of my…
SAS Enterprise Miner: Not for the faint of heart (or Mac owners)
A few years ago, when I was at USC, I tried to get a desktop version of Enterprise Miner to run on a virtual machine on my Mac and that never happened, although I did get it working on a Windows machine I had at home. Last week, I wrote about my failed attempt to…
Excel for regression analysis: What a surprise!
I wouldn’t normally consider Excel for analysis, but there are four reasons I’ll be using it sometimes for the next class I’m teaching. First of all, we start out with some pretty basic statistics, I’m not even sure I’d call them statistics, and Excel is good for that kind of stuff. Second, Excel now has…
Transcript (with a couple of ‘ands’ taken out and sans the hand waving):
What I wanted to talk about, though, was just in time design and programming. I read something from IBM about 10 years ago, and I was really impressed because I thought they were kinda ahead of their time, and I was surprised that it came from a big company. The idea is that you do programming, you do design, as you need it. Often people will see things that I put on my blog, things that I’m working on, and say very insightful correct comments that “you need to do this”, “you need to do that”. And they’re absolutely right: the reason we haven’t done it, whatever it happens to be, is that we’re a really small company. So if we’re, say, working on the storyline, and we’ve got the movies done, and they go from the movies to an input page, where they have to answer a math problem, and then they go to study something before they take a quiz to go back into the story… each of those parts needs to be done. Yes, there’s probably better ways to do the quiz than SurveyMonkey – one of the things I spent a lot of time doing was replacing the way we had originally done the quizzes – but until we’ve tested out whether that kind of design is what we want to do, working on perfecting each individual part of it is probably not the most cost effective use of our time. And cost-effective use of our time is something my next video blog is about…
What an incredibly nice thing to do. Thank you.
Ah, the Kaizen of programming. I agree iterative development is the way to go because it allows all kinds of feedback loops to be baked in. The downside is every new iteration with the client gives them a chance to feature creep the hell out of it if they feel they have the chance to (which could be a good or bad thing depending on the circumstances).
On large scale projects, it’s not uncommon at all to prototype a product in Ruby on Rails then go back later and rewrite it in Java for performance (if it really needs to scale). Twitter did this.
Iterative development is the _smart_ way to do it.
However, if you post a blurb of code on your blog specifically discussing its problems, be prepared to hear what’s wrong with it, regardless of your stage of development. 😛
Honestly, I *appreciate* hearing what is wrong, because there is no guarantee that when we get to that state of development we will think of everything.
On the scope creep – it also prevents us from the opposite. I’m working on a project now where I can think of all kinds of cool stuff but maybe the client wants bare bones.
AnnMaria: my pleasure. My hands are happy and it turns out to be fairly easy to transcribe with html5 video and 0.5x playback on youtube :).