1 Comment(s)

1. Another great episode. What follows are notes as I listened.

   Word of the day/week… in this episode it is actually a phrase… BUT that is being much too literal.

   I like that you pointed out that “smaller” projects do not require the same effort as “larger” projects - specifically: Use Cases.

   I use a calculator program in my courses - handling the 4 common math symbols. It is small AND any person in college should “know” the hows/whys - but converting it to programming concepts does present enough of a challenge that 200 level students do struggle.

   Because of this - I think the “size” of project is also dependent on the skill level of the programmer/developer. Less skills = more structure required to the process…enabling them to grasp the concept.

   Concept of Actor (as defined in this episode) is something that I have tried to get across to students - but they do struggle to conceptualize “things/people”. I don’t use the term - rather I use the object: server, computer, person. That seems to help.

   The bullet list IS how most people I have worked with - “start a project”. That brainstorm usually then splits into required items, would likes, and the 3rd batch “maybes or unlikely”.

   The example of Paypal NOT being a use case - is eye-opening! I would considered it one of those “external actors”.

   The concepts of “campaign” and “thinking about actor/use cases” has me thinking about the project I am beginning at work. Mind is working.

   I like the concepts of people focusing on their smaller tasks and the software “doing” the work.

   Concept of NO and qualifying prospects — The 80:20 rule comes to light.

   In listening to your discussion on identifying prospects - I almost think I might require listening to your podcast to understand the “process & discussion” that takes place to define a project. I don’t believe students know how much effort is really necessary… the “let’s start typing” concept that most think is how to get a project off the ground.

   Identifying authority and closing sale - especially closing sale — tough part for non-sales person. I remember this from working in/managing retail store. My sales people had varying degrees of success, even after training/practice sessions. “Will that be cash or credit”… is a tough step for many people.

   OK - writing code to enable UML Lounge characters to have movement/positions is great. But… Curtis almost died… Martin… you have to “warn him”… As much as Curtis wants to edit… It’s great to hear what sounds like “real time”. I really think this is better than more scripted/processed productions.

   Candidate design != Demo != final application

   John Burns | Jan 1, 2009 | Reply

Post a Comment