File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Agile and Other Processes and the fly likes Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark ""mistakes hide in complexity"" Watch ""mistakes hide in complexity"" New topic
Author

"mistakes hide in complexity"

Jeanne Boyarsky
internet detective
Marshal

Joined: May 26, 2003
Posts: 30501
    
150

Quote from page 80 of "Leading Lean Software Development":
In a nutshell, mistakes hide in complexity, and they are exposed in simple, well-factored code

Clearly this quote applies to making the code readable. What other areas can you think of where simplicity matters?

For example, I think of architecture.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
Mary Poppendieck
author
Ranch Hand

Joined: Oct 04, 2006
Posts: 62
Here are some places I see simplicity matters:

1. Too many features in a code base. Extra, unneeded features are rampant, and and they dramatically drive up costs.

2. Architecture needs to be simple, and also loosely coupled.

3. User interaction. Simplicity rules!

4. Dependencies in the schedule - why not decouple a schedule into logically decoupled workflows instead of creating a complex schedule with lots of dependencies.

5. Code, of course, as you mentioned, must be simple.

6. Simple workflow - getting something done should not involved a complicated trip to innumerable specialists, but a simple path through the system

I'm sure there are a lot more....


Mary Poppendieck
Author of Lean Software Development, Implementing Lean Software Development, and Leading Lean Software Development
David Newton
Author
Rancher

Joined: Sep 29, 2008
Posts: 12617

Mary Poppendieck wrote:1. Too many features in a code base. Extra, unneeded features are rampant, and and they dramatically drive up costs.
I see what you did there.

Other facets of simplicity:

- documentation
- development (and specification) processes
- infrastructure issues (how hard is it to get what you need)
- QA/UAT/post-deploy issue tracking/resolution
Jeanne Boyarsky
internet detective
Marshal

Joined: May 26, 2003
Posts: 30501
    
150

David Newton wrote:
Mary Poppendieck wrote:1. Too many features in a code base. Extra, unneeded features are rampant, and and they dramatically drive up costs.
I see what you did there.

LOL!
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: "mistakes hide in complexity"