Archive for the ‘Software and Science’ Category

Book Stack Dump, Day 1

Wednesday, June 4th, 2008
Book abbreviations correspond to titles on the picture from this link:
Cooperative Multireading Revisited and Started

POSA2: The importance of understanding middleware.

POSA5: Design: Thinking before building.

AMP: Think concurrently - a skill.

EIP: Learn technology: goal to apply it effectively. Integration via messaging - use patterns to leverage forthcoming technologies.

MM: Processes and threads: an OS view.

SC: Great divide: Discipline/Control vs. Agility - all good work done in the middle. Project-dependent approach. Dad style management. Information Age vs. Industrial Age management.

ASS: A window to a larger world. What to know if you want to be a support manager.

SM: Maintenance is 70% of life-cycle cost. Education misses software change.

CC: It takes 5-15 years for research to come into practice. Self-taught programmers need a formal reference book.

RP: The need to understand distributed middleware and object technology. Projection of Patterns to technology link the patterns.

MES: 3DES.

OOM: Philosophy of object-oriented methods.

TIS: Importance of fundamentals of long-term validity vs. specific products. Transactions in OS.

NAT: Network analysis is a part of problem solving skills. Independence of analysis techniques from software analyzers.

PT: Non-Chomsky systems and non-canonical parsers? Parallel parsing? Find new ways to use parsers in pattern recognition?

CW: More and more criminal code than before.

PNA: Need to discuss networks free from politics and market. Patterns lead to the collapse of complexity. Emergent orthogonality from cognitive shift.

CA: The need to overcome ignorance in hardware, understanding of the total software/hardware system and quantitative approach to ground thinking.

GC: Lifetimes can no longer be predicted manually. Manual lifetime control limits OO modularity.

CS: First-order information hiding (pure OO) is restricted to state transformations (no instances of ADT are allowed in the language). Second-order hiding allows the definition of algebras on ADT (additional operations). Class mechanism can be used to describe ADT but not the way around (the lack of static properties in class definitions). OO information hiding is the mix of first- and second order. Object - first order model. Second-order models provide access to internal state (C++/Java).

- Dmitry Vostokov @ SoftwareGeneralist.com -

Cooperative Multireading Revisited and Started

Wednesday, June 4th, 2008

I wrote already about cooperative multireading technique in another blog:

Managing Reading via Cooperative Multireading

This week I started testing it and found that 30 books for one hour is too much for me and finally selected 20 books rich in concepts that I own but have never opened to read. I excluded books that I started reading some time ago but never finished and books heavy on source code and hands on practice. Here is the picture of selected books:

I tell you that the first session was a success and I even managed to write notes. These will be published after each reading session. The notes have their own code name Book Stack Dump.

Today it was mostly foreword and preface pages :-)

- Dmitry Vostokov @ SoftwareGeneralist.com -