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
Reading JSON data saved in a column and other SAS string function tricks
Sometimes data changes shape and type over time. In my case, we had a game that was given away free as a demo. We saved the player’s game state – that is, the number of points they had, objects they had earned in the game, etc. as a JSON object. Happy Day! The game became…
Wolfram asks- why teach multiplication?
If you have not listened to the TED talk by Conrad Wolfram, I highly recommend you do. If you have any interest in math education, the odds are great that his talk is far more important than anything else you could possibly doing in the next 20 minutes. If you think the name sounds familiar,…
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…
The Sea Monkey Effect prevents robot uprising
Since I have written about odds ratios and logs lately, I was going to write about the natural log of the odds ratio, however, random events have caused me to do otherwise. I read an interesting blog by Adam Jackson lately, in which he is concerned that robots will take over the world. At the…
Maybe you *can* use SAS to teach art majors
I was supposed to be teaching statistics to undergraduate Fine Arts majors this semester but I’m going to Santiago to open a Latin American office for 7 Generation Games instead. I’m a bit disappointed because even though when I was younger and got asked at cocktail parties what I did for a living, I would…
How to compute a standard deviation and control chart when you don’t have raw data
It ought to be easier than this and perhaps I could have found an easier way if I had more patience than the average ant or very young infant. However, I don’t. Here was the problem. I wanted control charts for two different variables, satisfaction with care, surveyed at discharge, and satisfaction with care 3…
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 :).