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

Exercise: Prototyping and Creating Mock-Ups

We were tasked with designing a test-free search page mock-up for individuals who were unable to read. We were first required to create a paper prototype and then use an online tool, Balsamiq. I found the exercise very interesting as it forced me to refine all my ideas into one, single representation. It also involved selecting the most important requirements as we were under a time constraint. I found the paper prototype process slightly easier a using Balsamic introduced constraints, in that I had to create my design choosing from the icons within the Balsamiq tool as opposed to creating my own. I found this exercise very useful and I will aim to introduce quick prototyping in my future roles when applicable.
Post a Comment
Read more