Skip to main content

Week 6 Lecture - Reflection of Fishman "They Write the Right Stuff" (1996) Reading


During the lecture, we reflected on the assigned reading: Fishman, "They Write the Right Stuff" (1996)

Summary of Paper


  • The NASA process stifles creativity but that is the point
  • People working at the company have to channel their creativity into changing the process not changing the software
  • 12 of 22 members are women
  • They work strictly 8-5 unlike coders unlike in companies such as Microsoft where late nights are common
  • Its all about the process that allows them to work normal hours, stay on budget and deliver on time

  1. The product is only as good as the plan for the product - plan the most minute detail before commencing writing the code - their requirements are almost " blueprint like detail
  2. The best teamwork is rivalry team work
  3. Have a database on why, how, when etc. code was changed and also a database describing every error dating back 20 years. They’ve accumulated so much data that they’ve been able to create software to predict future errors
  4. Don’t just fix the mistakes - fix whatever permitted the mistake in the first place





Discussion

  • The process at NASA stifles creativity but is there not still a degree of creativity? Is creativity not involved in anything that requires change?
  • Creativity just happens differently - locked in early on
  • Not a normal industry
  • This makes sense in high risk industries e.g. pacemakers, nuclear plants
  • Some forced by regulation
  • May not work in other industries which need to adapt quickly, need to experiment, fail fast etc
  • Engineer who left the org did not enjoy working in the jockey, pizza environment as he had become indoctrinated in this culture
  • Quality, Cost, Time, Scope
  • Where are we with the variables
  • This org is optimizing?
  • Quality is fixed
  • Cost is a variable
  • Scope - Fixed primarily, overall goal stays constant
  • Time: Variable if necessary- not a free variable, they don’t want to use it as a variable but if they identify a flaw they will pull release date


Comments

Post a Comment

Popular posts from this blog

Iona Technologies

·        Iona was founded in 1991 by Chris Horn, Sean Baker and Anrai O’Toole ·        The company progressed from a Trinity campus company, releasing Orbix in 1992 and going public in NASDAQ in 1997 ·        Trinity College Distributed Systems Group (DSG) was a small group of academics and engineers conducting research and development into the problem of inter-network computing systems, essentially connecting systems which were developed as independent systems to work and communicate with one another ·        Their research was initially supported by Trinity and then the EU ·        They took a brave leap from academic to the commercial world due to the attractive opportunity of industries like banking and telecommunications embracing networks and internets ·        Iona found that their c...
Post a Comment
Read more

Week 2 Design thinking - Build the right thing

This week focused around building the thing right as opposed to building the right thing. Great design has always been concerned with the whole experience of interaction. One of the most interesting topics emerging from the class was prompted by a quote from Alan Cooper. It prompted discussion around what do you get when you cross a computer with a camera? A phone? A plane? With a car? A ship? You get a bigger computer.   The products we use on a daily basis are becoming ever more like software. Allen stressed that we need to develop an annoyance and radar for bad design and an appreciation for superior design. He showed us a variety of good and bad design examples and showed examples of how users will highlight the problems in your products or else they will leave marks e.g. a sign telling the user how to interact correctly with a product / service During the lecture, we also watched a video "Inside IDEO" which followed the IDEO design team revolutionizing the ...
Post a Comment
Read more

Designing a Robot

In week 9, we worked in small groups to create a robot using an instruction manual and upon creating our robot, we were tasked with creating a "run" function so that our robot could drive around and "guard a base." (for the purpose of the class, the base was a large white box) This exercise was great fun, but at times stressful as we were required to create our robot within a short time constraint. To create our robot within the allotted time, my group divided the tasks amongst us. One individual called out the required materials needed and where they were to be placed, one found the necessary materials and two individuals put the robot together. As requested by our lecturer, we switched roles frequently so that each member got experience working on each of the tasks required. Dividing the roles out amongst ourselves enabled us to create our robot more quickly than if we had completed each of the tasks together as a group.
Post a Comment
Read more