Sponsored links


Valid XHTML 1.0!
Valid CSS!
Product: Book - Paperback
Title: Regular Expression Pocket Reference
Publisher: O'Reilly
Authors: Tony Stubblebine
Rating: 4/5
Customer opinion - 4 stars out of 5
All that and a bag of chips


I found this guide very useful. I learned a whole slew of new expressions to incorporate into my everyday vocabulary. To think, I'd been wasting my time saying things like, "Wicked cool!".
Stubblebine gives it to you in an easy-to-understand format. If he had other books I'd buy them (plus, I understand from some women in the geek community that he's a total babe!). Two thumbs up!



Product: Book - Paperback
Title: The Data Warehouse Lifecycle Toolkit : Expert Methods for Designing, Developing, and Deploying Data Warehouses
Publisher: Wiley
Authors: Ralph Kimball, Laura Reeves, Margy Ross, Warren Thornthwaite
Rating: 4/5
Customer opinion - 4 stars out of 5
Very good introduction to data-warehouse modeling


you will get a very good introduction to data-warehouse modeling, you will need some basic SQL-knowledge and a little bit patience during reading (the book could be a little bit shorter)



Product: Book - Paperback
Title: Don't Make Me Think: A Common Sense Approach to Web Usability
Publisher: New Riders Press
Authors: Steve Krug
Rating: 5/5
Customer opinion - 5 stars out of 5
A small gem of a book for anyone doing Web development


My new favorite book on Web usability design and user testing. This is a short book (I like books that get to the point without a lot of padding!) that promotes some real commonsense design principles and cuts through much of the nonsense that passes for site design today. It also has a great couple of chapters on usability testing that demystifies the process and makes it accessible to anyone doing Web work.



Product: Book - Hardcover
Title: The Unified Software Development Process
Publisher: Addison-Wesley Professional
Authors: Ivar Jacobson, Grady Booch, James Rumbaugh
Rating: 1/5
Customer opinion - 1 stars out of 5
A reader in the Netherlands


I have worked on OO since 1987 and have come to the conclusion that objects and use cases alone are not sufficient for success (I suspect that they may be necessary but that is another discussion). The UML and use cases are rooted in the object mindset. It is not possible to design and maintain large systems with objects and use cases. A use case is by definition an interaction session with an actor. What happens if there are very many actors, each one doing its own thing? The answer is anarchy.
What we need is a revision of the object paradigm. In particular, use cases are OK but before we discover them we must concentrate on viewpoints and requirements (UML 2.0 here we come).
The major weakness in Jacobson's book is the total lack of architecture. It is not true when the authors claim that use case drive architecture.
The Boundary-Entity-Control patterns is good but have the authors seen what is being done at CMU in the area of PAC (Presentation Abstraction Control) model?
Concluding, the example in the book is worn out by now (ATM). The UML has not kept abreast of new developments such as core process modelling, architecture and patterns. Many of my customers are beginning to reach the boundaris of UML and the RUP.