NOTE:
So I accidentally read the last chapter of The Design of Future Things and blogged about it. I felt like I did good work so I'm leaving it in here.
Extreme Programming
By: Ron Jeffries; Ann Anderson; Chet Hendrickson
Publisher: Addison-Wesley Professional
Pub. Date: October 16, 2000
Chapter 19 : Steering
Since XP's goal is to put out high value software in time, steering is needed to ensure that it does. To this end, XP recommends keeping track of stories, making accurate estimates, and to proceed at the pace your measuring while making sure that essential customer features are not cut.
Chapter 20 : Steering the Iteration
XP emphasizes that the main point of each iteration is to finish stories.
Therfore, it offers recommendations on how to do that:
The first recommendation is to get some stories done completely rather than to get all stories mostly done.
The second recommendation is to continuously improve estimates based on midproject feedback, project resources, and reflection.
The third recommendation is to track story progress regularly at meetings or with a dedicated tracker personnel, preferably someone who is not judgmental and can motivate others to perform better without hard feelings coming out as a result.
Rotating the tracker or using the customer as a tracker is discouraged.
Tracking helps the project stay on track, obviously.
Chapter 21 : Steering the Release
Two things are needed important at the release level:
1) When to release
2) What is released
Controlling the scope of the project is necessary in order to deliver on time which is a large measure of success at the managerial level.
XP emphasizes prioritizing essential story cards with the most points and completing those first, keeping track of the time to complete specific tasks with accurate estimates and using those measurements to project the amount of points that can be accomplished before the release. This prioritization allows the scope to be controlled and stories can be deferred at the end, if need be.
The Design of Future Things
Design of Future Things
By: Donald Norman
Publisher: New York Basic Book
Pub. Date: November 2007
Chapter 7 : The Future of Everyday Things
In this chapter, Norman closes his book with a set of projections about what the future will actually be like with regards to "smart technology."
Norman begins by discussing the "magic mirror" of tomorrow that will communicate with other devices, be used to shop for clothes and display your image in them, and even change your physical appearance on the mirror. He discusses this to make the point that what seemed like magic yesterday may become our future.
Norman highlights how quickly things have changed by bringing up his first book, "The Design of Everyday Things" where he discussed design problems with doors and stove tops. Now though we confront intelligent appliances, vacuuming robots, and recommendation systems.
Norman also talks about 3D printers that synthesize objects out of thin-air.
He mentions the materials revolution taking place in nanotechnology, biotechnology, and and corresponding advances that blur the line between man and machine.

Norman also makes recommendations about how robots should be used in the near future. Mainly he claims that robots should be specialized for their domain and communication with users minimized so that failure in communication is minimized and expectations are known on the side of the human actor. He claims that robots could best be used for education, entertainment, and dangerous jobs and that general purpose robots are far off from being implementable.
Furthermore, Norman observes that while biological change is naturally conservative, the mind itself is malleable. Hence, mankind will tend to bend to the flow and ebb of technology rather than technology bend to the whims of men.
Finally, Norman claims that design should incorporate aspects of science and art and that education and application of design should be general in nature rather than applied by focused specialists.
Inmates Are Running the Asylum,
The: Why High-Tech Products Drive Us Crazy
and How to Restore the Sanity
By: Alan Cooper
Publisher: Sams
Pub. Date: February 24, 2004
Part 1 - Computer Obliteracy
Chapter 1 : Riddles for the Information Age
Cooper starts his book by introducing a few cases displaying the frustration of working with computer and their inherent difficulties in computer human interaction.
Each of these cases show how digitization and the expansion of computers into various objects and devices has transformed their behavior.
Cooper starts with the case of an airplane crash that resulted from an inexpressive
navigational system that didn't ensure the correctness of the displayed information.
Cooper also explored alarm clocks, cameras, cars, banks, and even warships.
Cooper blames companies for putting in needless features to provide the illusion of advancement and sophistication to market their products. He also likens acceptance of these products in the trend of computerization to a frog not noticing he is sitting in a slowly boiling pot.
Next, Cooper touches in the incomprehensibility of computer interfaces that don't take the human side operator into consideration. He claims the difficulty in understanding these systems that is apparent in the common "mustachioed" man produces a kind of "technological apartheid."
Cooper also mentions that inconsiderate software also causes economic losses like those found in the "IFE" system on airlines that forced flight attendants to walk up and down the aisle more than necessary. (The flight attendants would just short circuit the system at the start of every flight.)
Cooper then coins the term "Techno Rage" to describe the frustration people experience in using bad computer human interfaces.
Cooper also observes that the tech industry seems to believe that any problems with how difficult computer technology is to use, most of which industry denies, will be solved by more advanced technologies. Cooper claims that this is false, because more advanced and complicated technologies will only further confuse the average everyday user. He proposes the process of building the technology needs to be fixed.
After covering these cases and observations, Cooper comes to his main point:
That the experts and apologists for technology within companies hold the reigns to guiding the development of products and as such, issues of usability and approachability of software for common people are ignored.
In more concisely,
"The Inmates are Running the Asylum."
Cooper ends the chapter by explaining his liberation from the process of programming that allowed him to come the above revelations. Cooper also explains that programmers need to do interaction design before they actually begin to code.
Chapter 2 : Cognitive Friction
Cooper starts this chapter by introducing the idea of "cognitive friction" or the resistance encountered by a human mind when it engages with a complex system of rules that changes as the problem changes. Apparently, objects that enter into meta-states frequently, like a computer, tend to be high in cognitive friction which increases frustration.
Cooper then begins to advocate "design" or, more specifically, "interaction design" which includes all things that directly affect the end user of the software.
Cooper claims this design should be done by dedicated "interaction designers" that can steer the focus of the team from software into an enjoyable end product used by humanity.
Cooper goes on to claims that most design is done unwittingly, by convention or tradition, and most times, the end product isn't even used by those who made it.
The software design usually revolves around decisions of what is easy to produce rather than what is easy to use.
Cooper then discusses the differences between interface and interaction. He likens putting an interface to cover bad software to putting an "Armani suit on Attila the Hun." Essentially, just doing interface design is whitewashing the problem. Instead, Cooper advocates doing behavioral design that influences underlying code structure and outputs that will also feed into the interface. He goes further in saying that conceptual design should be done that examines the values and needs of the user and how those needs should be integrated into the software.
Next, Cooper asserts that cognitive friction is a natural part of software because its immediate use cannot be observed and understood at first glance or preliminary manipulation. The user must commit to an action and feel its effects before it is understood. In other words, its usage cannot be intuited which can make the user feel dumb.
Cooper then explains why software has been so prolific and widely used by painting the image of a dancing bear:
"The wonder isn't that the bear dances well but that the bear dances at all."
The uses of software is both incredibly useful and wondrous, if not cantankerous.
Technology advocates and apologists insist that the "dancing bearware" is great and by necessity complicated and difficult to use due to the intractability of the problem domain, but Cooper argues differently.
He claims that people just accept the apologists explanations while software could all the while be better designed. Hence the source of the cognitive friction is in the maker rather than the creation.
Cooper cites that it's easier to add features than to make software easier to use mostly because software development doesn't have a clear built in negative feedback loop for new features that are usually provided by physics and cost of materials.
This lack of a negative feedback loop leads to software that is packed with useless and confusing features that crowd the interaction space. In a word, bloatware.
Cooper mentions that society can be divided into apologists and survivors, with obvious connections to their preferences and attitudes toward technology.
Apologists are attracted to computers because of the innate difficulty of the technology and the height of the cognitive reward for solving the task.
Survivors, on the other hand, are trapped into using computers. They know what's easy and hard and the find using computers hard and frustrating.
Cooper claims that people react to cognitive friction in the same way:
Use the fewest possible feature you understand.
Finally, Cooper covers the "Euphemism Pyramid" composed of naive users, computer-literate users, and power users. These terms hide the truth of how software developers categorize and judge the people they develop for. These judgments reinforce the "software apartheid" and encourages a view that people should adapt to the technology rather than the developers and technology adapting to the needs of the users.
Mythical Man-Month, The: Essays on Software Engineering, Anniversary Edition
By: Frederick P. Brooks Jr.
Publisher: Addison-Wesley Professional
Pub. Date: August 02, 1995
Chapter 1 : The Tar Pit
In the introductory chapter of Mythical Man-Month, Brooks likens the struggles of software engineering to the struggles of "great beasts" to escape entrapment in a tar pit: The problem is sticky and hard to understand and many have fallen in but few escape the problem they find themselves in despite their girth or skill.
Brooks explains that the development of software that is more than merely a "program" but is also a programming product and system inherently introduces costs, complexities and hence problems that figure into complexity of scheduling of making such software. However, many of these complexities in producing "programming systems products" (that are generalized, tested, and documented) or "programming systems" (that are systems of interacting programs) are often underestimated by programmers.
Brooks ends the introductory chapter by discussing the joys and woes of the "craft" of programming.
The joys include:
The joy of making things.
The joy of useful things for others.
The joy of making complex/intricate/puzzle-like things work.
The joy of learning.
The joy of working in a tractable medium (where there imagination is dominant)
The woes include:
The woe of having to perform perfectly.
The woe of being unable to control the circumstances of the work.
The woe of having to depend on others.
The woe of debugging.
The woe linear of convergence where more difficult bugs take more time to find than the first.
The woe of working on a product that is obsolete on completion.
Chapter 2 : The Mythical Man-Month
In this chapter, Brooks explore the titular problem addressed by the book, namely that software projects are often overschedule and that assigning more men to a problem does not necessarily (and not even in the majority of cases) decreases the time left to finish the project. Brooks asserts that assigning more men to a project may even increase the time to completion because of the need to train and familiarize the new men with the current project as well as increase the time to communicate between the team.
Brooks outlines several "fallacies" that cause project schedules to be underestimated:
The first fallacy is that our ideas are perfect, hence, the implementation of these perfect ideas should encounter only minor difficulties. In other words, we are overly optimistic. Brooks makes an observation that programmers tend to be optimists most likely due to the sometimes frustrating nature in the details of programming that sifts out those that are most focused on the end goal. This tendency leads to underestimates of the amount of time to finish a project.
The second fallacy is that effort corresponds to progress. Brooks cites the man-month myth that by applying more men to a project, or effort, the amount of progress, or time remaining, should correspondingly decrease.
However, Brook states that this is only true if the task being undertaken can be split and assigned among workers with no communication needed between them and that the task has no partitions or expertise needed in implementation.
Brooks makes the recommendation that more time should be allocated to the system for testing (1/4 overall time) and that it's better to allow for more project time than to cut features or add manpower to a project.
Chapter 3 : The Surgical Team
In this chapter, Brooks tackles the problem of how to divide work and coordinate work on large software products where a large team is needed.
He makes the recommendation of putting together a "Surgical Team" where roles and responsibilities have a clear separation and where value can be added to the project without waiting on another roles and where authority is strictly defined.
Because a surgical team is small and the experienced members are put in strategic positions, efficiency and skill sets are maximized rather downplayed under the broad categories and restrictions of management.
The roles include the following:
Surgeon - Chief Programmer
The copilot - less experienced Chief Programmer
The administrator - manages personnel, money, space, and other matters that would otherwise tie up the surgeon
The editor - generates documentation
The secretaries - handles correspondence and non-product files for the editor
The program clerk - Maintains technical records of the team
The toolsmith - Provides tools, libraries, software, etc. for the team
The tester - writes test cases, system tests, and assists with debugging
The language lawyer - finds neat and efficient ways to use the language to do difficult, obscure, or tricky things.
The team organization allows the team to act as one and since all the roles are equal, compromises and different points of view increase the quality and cooperation
of and on the project, respectively.
Brooke closes the chapter with a discussion of how to scale up the method by essentially saying that multiple surgical teams can be created and that the surgeon of each team communicates with each other for coordination.
Discussion:
Extreme Programming:
The extreme programming chapters were repetitive and boring (again).
The entire section on "steering" was already covered in story estimation and the need to prioritize was already emphasized earlier.
The only new idea was the one where using a specific tracker to monitor story was suggested and even then common sense could have been applied in how to select a tracker.
I have nothing else to discuss.
Design of Future Things:
This final chapter of future things was undoubtedly the most speculative but in a strange way, perhaps the most informative. His recommendations for the progression of technology and our way of approaching it was thought provoking and maybe even controversial with his recommendation of conforming to technology.
The revolutions in material science and the convergence of man and machine is particularly thought provoking and images of science fiction masterpieces like "Ghost in the Shell" and "The Matrix" quickly come to mind. It would have been easy for Norman to diverge from this near-future focus into wild predictions of the far of future and the potential of humanity's symbiosis with high technology, but fortunately he resists and keeps his discussion focused.
The discussion on how devices communicate with each other, particularly in terms of recommendation of action for a common user, I think, could be drastically expanded on in another chapter. In light of his descriptions, I think we should minimize the amount of recommendation systems that enter into our lives simply because they are a distraction from what might be called a "natural reality." I think diverging from natural reality is somewhat harmful, mostly because our brains, while malleable, are designed/evolved to be interact with our natural reality and the fact that our expectations in social interaction cannot keep pace with our advances in speed and range of communications technologies.
The Inmates are Running the Asylum:
Cooper has some great insights on the psychology of software developers and industry in general that shouldn't be ignored outright. His advocacy of interaction design before coding is the right approach, I think. This keeps the end user and goal of the system in mind and keeps the developers from designing for just the computer and its needs.
His emphasis of the "software apartheid" is probably a bit extreme and I think people are more adaptable than he gives them credit for. Nonetheless, his focus on designing for people is ultimately correct, in my mind.
His observations on the inherent cognitive friction in software are useful and it leads me to think about how software systems and interfaces could be restructured to suit human cognition and need for affordances like Norman advocated.
Mythical Man-Month:
Reading Brooks' writing is a joy when compared to the other two authors for one principal reason: He writes with a sense and appreciate of art of writing. He knows how to write and to make it enjoyable. He writes with interesting metaphors that entertain without being too wild or that go outside the bounds of comparison.
The information he offers, while in itself is not terribly radical or ground breaking, is written in such a way that it sits well on the palette of your mind.
For example, Brooks could easily have written that underestimating the time to implement a program is because programmers are hopelessly optimistic and bad metrics are used in management. But this would have been dry and boring. Instead, he illuminates the fallacies that cause those problems and slowly reveals the effects of these fallacies as the ones stated above.
The idea of the surgical team was interesting although I might question the necessity of many of the roles, like the language lawyers. Such positions may be out-dated but I'll reserve my judgment given my inexperience.