Software Modularity: Paradoxes, Principles, and Architectures
←Older revision | Revision as of 07:50, 23 October 2012 | ||
Line 22: | Line 22: | ||
October 3, 10:00 - 11:00 | October 3, 10:00 - 11:00 | ||
- | I am about to publish new book about [[Paradoxes of API Design | + | I am about to publish new book about [[Paradoxes]] of API Design (not a chapter as was in [[TheAPIBook]], but a complete book with twenty chapters revealing sort of paradoxial observations about [[API]] design) and I'd like to promote it a bit during [[JavaOne2012]]. Andrzej Olszak agreed to help me. His deep theoretical knowledge of design principles useful for producing viable architectures will be confronted with [[User:JaroslavTulach|my]] paradoxes. Stop by to win a discount for the [[Paradoxes]] book. |
+ | |||
+ | I really enjoyed Andrzej's part. He talked about so many interesting things. For example he mentioned that there are multiple reasons to [[modularize]] your application and each of them leads to completely different architecture. | ||
== Patterns for Modularity: What Modules Don’t Want You to Know == | == Patterns for Modularity: What Modules Don’t Want You to Know == |