Engineering Software as a Service Quotes

“False. While imitating best practices of WSC could lower costs, the major cost advantage of WSCs comes from the economies of scale, which today means 100,000 servers, thereby dwarfing most internal datacenters.”
― Armando Fox, Engineering Software as a Service: An Agile Approach Using Cloud Computing + $10 AWS Credit

“forewarned is forearmed!”
― Armando Fox, Engineering Software as a Service: An Agile Approach Using Cloud Computing + $10 AWS Credit

“SOA actually means that components of an application act as interoperable services, and can be used independently and recombined in other applications. The”
― Armando Fox, Engineering Software as a Service: An Agile Approach Using Cloud Computing + $10 AWS Credit

“The goal was to discover methods to build software that were as predictable in quality, cost, and time as those used to build bridges in civil engineering.”
― Armando Fox, Engineering Software as a Service: An Agile Approach Using Cloud Computing + $10 AWS Credit

“Finally, unlike Plan-and-Document, in Agile you revise code continuously to improve the design and to add functionality starting with the second iteration.”
― Armando Fox, Engineering Software as a Service: An Agile Approach Using Cloud Computing + $10 AWS Credit

“if you cannot describe the responsibility of a class in 25 words or less, it may have more than one responsibility, and the new ones should be split out into their own classes.”
― Armando Fox, Engineering Software as a Service: An Agile Approach Using Cloud Computing + $10 AWS Credit

“The five letters of the SOLID acronym stand for: Single Responsibility Principle: a class should have one and only one responsibility; that is, only one reason to change. The Lack of Cohesion Of Methods metric indicates the antipattern of too large a class. Open/Closed Principle: a class should be open for extension, but closed against modification. The Case Statement design smell suggests a violation. Liskov Substitution Principle: a method designed to work on an object of type T should also work on an object of any subtype of T. That is, all of T’s subtypes should preserve T’s “contract.” The refused bequest design smell often indicates a violation. Dependency Injection Principle: if two classes depend on each other but their implementations may change, it would be better for them to both depend on a separate abstract interface which is “injected” between them. Demeter Principle: a method can call other methods in its own class, and methods on the classes of its own instance variables; everything else is taboo. A design smell that indicates a violation is inappropriate intimacy.”
― Armando Fox, Engineering Software as a Service: An Agile Approach Using Cloud Computing + $10 AWS Credit

“The purpose of velocity is to give all stakeholders an idea how many iterations it will take a team to add the desired set of features, which helps set reasonable expectations and reduces chances of disappointment.”
― Armando Fox, Engineering Software as a Service: An Agile Approach Using Cloud Computing + $10 AWS Credit

“When Ruby programmers say that some class “quacks like an Array,” they usually mean that it’s not necessarily an Array nor a descendant of Array, but it responds to most of the same methods as Array and can therefore be used wherever an Array would be used.”
― Armando Fox, Engineering Software as a Service: An Agile Approach Using Cloud Computing + $10 AWS Credit