Aug 25, 2006
Previous Posts
Code is Design
- Being explict is better than being implicit
- Encapsulation is not security
- GWT and JDO on the Java App Engine
- Exploring Tail Recursion
- Demeter's law (suggestion) and tell don't ask - Part one, two, three
- Sweet Sequence
- Using Cyclomatic Complexity effectively
- OS as a registry for key bindings
- Linus on simple design
Agile
- Pair Programming Payoff
- Label activities, not people
- Fail Fast
- When Agile Estimation becomes pointless
Big Picture
- The Tragedy of Commons based Peer Production
- Open Source authors' struggle for compensation
- No software patents versus patent reform
- SOA in India
- ThoughtWorks on App Engine for Java
- SaaS is a distribution model, Cloud is a hosting model
- No Fresher Jobs? Don't despair.
- Survival of the hungriest
- Amazing Amazon!
- Save the internet
Knowledge Management
- Thoughts on wiki based documentation
- Knowledge Management Fallacies Series:
Usability
Books
- How applications learn. What happens after they are built?
- Who do you report to?
- Low cost editions of Refactoring Databases and DDD



1 Comments:
Yes, nice tool, but with a some limitations.
It is imposible to make notes to the sequence diagram. Sometimes, just a function calls is not enough to understanding
Post a Comment
<< Home