Modular Class Quotes

By making offers Modular, the business can create and improve each offer in isolation, then mix and match offers as necessary to better serve their customers. It’s like playing with LEGOS: once you have a set of pieces to work with, you can put them together in all sorts of interesting ways.

Keep Your Design Modular Modularity's goal is to make each routine or class like a "black box": You know what goes in, and you know what comes out, but you don't know what happens inside.

Summary of Design Heuristics Here's a summary of major design heuristics: More alarming, the same programmer is quite capable of doing the same task himself in two or three ways, sometimes unconsciously, but quite often simply for a change, or to provide elegant variation. — A. R. Brown W. A. Sampson Find Real-World Objects Form Consistent Abstractions Encapsulate Implementation Details Inherit When Possible Hide Secrets (Information Hiding) Identify Areas Likely to Change Keep Coupling Loose Look for Common Design Patterns The following heuristics are sometimes useful too: Aim for Strong Cohesion Build Hierarchies Formalize Class Contracts Assign Responsibilities Design for Test Avoid Failure Choose Binding Time Consciously Make Central Points of Control Consider Using Brute Force Draw a Diagram Keep Your Design Modular

The most important pillar behind innovation and opportunity—education—will see tremendous positive change in the coming decades as rising connectivity reshapes traditional routines and offers new paths for learning. Most students will be highly technologically literate, as schools continue to integrate technology into lesson plans and, in some cases, replace traditional lessons with more interactive workshops. Education will be a more flexible experience, adapting itself to children’s learning styles and pace instead of the other way around. Kids will still go to physical schools, to socialize and be guided by teachers, but as much, if not more, learning will take place employing carefully designed educational tools in the spirit of today’s Khan Academy, a nonprofit organization that produces thousands of short videos (the majority in science and math) and shares them online for free. With hundreds of millions of views on the Khan Academy’s YouTube channel already, educators in the United States are increasingly adopting its materials and integrating the approach of its founder, Salman Khan—modular learning tailored to a student’s needs. Some are even “flipping” their classrooms, replacing lectures with videos watched at home (as homework) and using school time for traditional homework, such as filling out a problem set for math class. Critical thinking and problem-solving skills will become the focus in many school systems as ubiquitous digital-knowledge tools, like the more accurate sections of Wikipedia, reduce the importance of rote memorization. For children in poor countries, future connectivity promises new access to educational tools, though clearly not at the level described above. Physical classrooms will remain dilapidated; teachers will continue to take paychecks and not show up for class; and books and supplies will still be scarce. But what’s new in this equation—connectivity—promises that kids with access to mobile devices and the Internet will be able to experience school physically and virtually, even if the latter is informal and on their own time.

You can accomplish it by thinking about your teaching as modular, by which I mean that what you do in the classroom consists of a series of different cognitive activities, each of which could be considered its own module, and any given class period is constructed by combining modules in ways designed to support both attention and learning.

Specific Architectural Topics Is the overall organization of the program clear, including a good architectural overview and justification? Are major building blocks well defined, including their areas of responsibility and their interfaces to other building blocks? Are all the functions listed in the requirements covered sensibly, by neither too many nor too few building blocks? Are the most critical classes described and justified? Is the data design described and justified? Is the database organization and content specified? Are all key business rules identified and their impact on the system described? Is a strategy for the user interface design described? Is the user interface modularized so that changes in it won’t affect the rest of the program? Is a strategy for handling I/O described and justified? Are resource-use estimates and a strategy for resource management described and justified for scarce resources like threads, database connections, handles, network bandwidth, and so on? Are the architecture’s security requirements described? Does the architecture set space and speed budgets for each class, subsystem, or functionality area? Does the architecture describe how scalability will be achieved? Does the architecture address interoperability? Is a strategy for internationalization/localization described? Is a coherent error-handling strategy provided? Is the approach to fault tolerance defined (if any is needed)? Has technical feasibility of all parts of the system been established? Is an approach to overengineering specified? Are necessary buy-vs.-build decisions included? Does the architecture describe how reused code will be made to conform to other architectural objectives? Is the architecture designed to accommodate likely changes? General Architectural Quality Does the architecture account for all the requirements? Is any part overarchitected or underarchitected? Are expectations in this area set out explicitly? Does the whole architecture hang together conceptually? Is the top-level design independent of the machine and language that will be used to implement it? Are the motivations for all major decisions provided? Are you, as a programmer who will implement the system, comfortable with the architecture?