About

deb goudy
teacher & computer department chair, episcopal school of dallas
programming, robotics, games, animation, 3D modeling

2 Responses to “About”

  1. Sue Says:

    December 22, 2008 at 10:25 pm

    Hi! I am so sorry. I know I have troubled you a lot with this enquiry. I am a student and I hope you could help me out with my research by just giving me the name of “efficiency expert” you mentioned in one of your posts on 13 December 2008 (on ADDIE). It sounds like this.. (under the line)
    (I thank you very much for your help)

    _______________________________________________
    What was wrong with it? Real work often doesn’t follow the plan that efficiency experts lay out:

    Creativity is often non-linear. Procedures that are rigid and linear stifle creativity, reducing the quality and innovativeness of the product. A rigid procedural approach may also drive away the most talented people.
    A problem that was generated in Step 1 may not show up until Step 4 or 5. A good model must allow for looping back to previous steps, possibly even starting somewhere other than at “the beginning”. Often design and development are iterative processes. Neither ADDIE nor the Waterfall Model seem to allow for that.
    Problems (bugs) are by their nature frequent and often unpredictable. They may be easy to fix or surprisingly difficult and time-consuming. And they don’t show up according to a planned schedule or procedure. They may pop up at the most inopportune times.

    Reply
    1. dgoudy Says:

      December 26, 2008 at 3:01 pm

      Most of the ideas I used from the Dreaming in Code book were from chapter 9: Methods. In that chapter, the author talks a lot about different programming models and methodologies. It’s a great book; I recommend that you read it. This discussion will be richer and make more sense in context of the work that was being done to develop Chandler, an open source program for managing personal information.

      Reply

Leave a Reply