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
Coding Tools to Make Life Easier
I was working on something for a client when The Invisible Developer walked into my office, looked over my shoulder at the code and said, “So, you’re a PHP programmer now?” I answered, “I’m a whatever-language-we-happen-to-need-at-the-moment programmer.” A year and a half ago, I took a look at Codecademy and was underwhelmed. It’s gotten mixed…
Learning from the mistakes of others
Three times within a very short period I have seen technology offerings that I thought were an epic fail. In one case I was a beta tester, in one, a regular user and in the third a personal friend of the founder. All of them, I thought, had brilliant ideas that fit a real need…
SAS Studio – Import Excel with Tasks & Utilities
It’s been about a year since I last looked at SAS Studio much – OKAY, LISTEN UP PEOPLE In my previous life, I taught for years at a small liberal arts college, with under 2,000 students. I also taught at a tribal community college with less than 500 students. In neither of those situations did…
It’s Amazing Any Software Ever Works
The Rocket Scientist and I just had our first martini in days. Actually, one of us (cough * me * cough) is not a big drinker, but still … Alcohol is against tribal law and I do believe in respecting the customs anywhere I am visiting. If I can’t respect your customs, I won’t go…
Use Title and Label Statements to Document SAS Code
“I don’t document my code because if you really understood the language, it should be obvious.” – Bob Bob is an arrogant little prick. Here are just a few reasons to document your code. Other people may need to modify it because, despite your assumed brilliance, there may be other people in the universe…
Computer Game Design: What I Know Now
These days, about half of my time is spent in management and collaboration, a fourth on writing code for a game and the remaining fourth on statistical analysis. This isn’t how I’d choose to divide my hours if I was in charge of the universe, but, that’s the way it is. Bwoo-ha-ha That is the…
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 :).