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.
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.
Anyone who wonders why there are not more women in technology, not more women startups should read the book, A strange stirring, by Stephanie Coontz about the impact the book The Feminine Mystique had on America. Like Coontz, I read The Feminine Mystique and found it kind of boring, although there were parts that resonated….
With the new SAS On-Demand for Academics, I presume there will be a lot of professors who have a teaching assistant, research assistant or intern preparing the data for examples for their classes. Or, you may be co-authoring a paper with one of your colleagues. Let’s suppose you are working on a SAS Enterprise Guide…
I wanted to learn how to use smashwords, for reasons completely unrelated to this blog, SAS or statistics, but I thought it would go much faster if I had an actual project to work on. I considered writing a serious book for researchers on SAS Enterprise Guide, but then I decided that I did not…
Let me just say off the bat that open data is awesome and there should be more of it available. This semester, I have been using SAS On-Demand in my statistics class and creating the data sets to meet students’ interests. Despite some people’s aspersions that I read on Twitter that some statisticians know no…
Been working with SAS a lot lately to get the data in shape for a new client. Here’s one of the problems I ran across. We want to get the average pay rate for people who got jobs as a result of our client’s services. However, when one of the people they served did not…
If you did not go to SAS Global Forum this week, here are some things you missed: Me, rambling on about the 13 techniques all biostatisticians should know, including the answer to: If McNemar and Kappa are both statistics for handling correlated, categorical data, how can they give you completely different results? The answer is…
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 :).