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
SAS Enterprise Miner: The Best Case Scenario
I’m in North Carolina this week at a class for professors on Advanced Predictive Modeling using SAS Enterprise Miner. This is the sort of statement that causes The Spoiled One & Co. to make faces that look like this: Despite my failure to impress fourteen-year-olds, I think the class has been well worth it. I’m…
More cultural relevance = lower academic achievement: WHY?
Before we went to Arlington, VA to get our hands on the National Indian Education Study , my colleague, Dr. Erich Longie, hypothesized that schools that had more cultural activities would have lower academic achievement. In addition to being an old friend, Dr. Longie is president of Spirit Lake Consulting, Inc. , a published author…
USDA is the biggest proponent of women in tech
I’m pretty certain that I’m a woman in technology. Last night, I was using SAS on a virtual machine through a remote desktop connection to prepare data from the National Hospital Discharge Survey for use in examples of MANOVA and multinomial logistic regression. Today, I was working on improving animation in the Javascript for a…
SAS Tip: Preventing Disaster When Variable Lengths Differ
Over the weekend, I wrote a post showing how SAS can be used to make what appears to be a complex problem quite simple. First of all, am I just being dramatic? Seriously, how can having your variable lengths differ be a disaster? Simple. You are merging by a variable that is a unique user…
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…
SAS: The . Manual
I stole that name from Chris Hemedinger for “The Missing Manual” because I thought it was hilarious. If you don’t program in SAS much then you probably did not think immediately, “Oh, . is the symbol for missing numeric data, how funny.” In fact, you are probably more like my daughter, Maria Burns Ortiz, who…
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 :).