emergent design

In it, I'll summarize concepts and draw conclusions from almost two years of writing and presenting about emergent design.

In the next installment, I'll continue discussing DSL techniques as a mechanism for harvesting idiomatic patterns in emergent design.

The next Evolutionary architecture and emergent design installment will wrap up the series.

In this installment, I started the discussion about using refactoring as a tool to help understand and identify emergent design.

When looking at the overall scope of the problem, try to isolate pockets that will tend toward emergent design techniques.

A portion of emergent design is the ability to see and harvest idiomatic patterns from existing code.

Several previous installments of this series focus on the obvious first step in emergent design: discovering idiomatic patterns.

One of the key enablers for emergent design is the ability to harvest and use the idiomatic patterns you uncover.

One of the goals of emergent design is to find idiomatic patterns of use within your application.

One of the difficulties for emergent design lies in finding idiomatic patterns and other design elements hidden in code.

Previous articles in this series have covered technical considerations for emergent design, but software designs don't occur in a vacuum.

First, many definitions of architecture exist in the software world (for better or worse), while emergent design currently enjoys less fame.

This works well for idiomatic patterns in emergent design because domain patterns are frequently declarative.

Developing skills in emergent design allows you to defer decisions until you have more context.

In this installment and the preceding one, I've discussed environmental concerns and impacts on emergent design.

Thus far, I've discussed emergent design in the context of the perfect-numbers problem.

This installment discusses how to estimate for emergent design, and how to make a convincing case for repaying technical debt.

One of the most common questions about emergent design is "How do you estimate for it? "

Emergent design falls in between these two extremes, but more toward the right than the left.

Agile methodologies that rely on emergent design try a different approach.

Next up: I talk about emergent design through test-driven development, which I've renamed test-driven design.

Emergent design implies the ability to find design elements in existing code.

Discovering these patterns is the key to emergent design.

What kind of projects benefit the most from emergent design?

The more expressive your design, the easier it is to modify it and eventually harvest idiomatic patterns from it via emergent design.

Which brings me back around to emergent design.

The real trick in emergent design is discovering these patterns.

Emergent design is a responsive, reactive way to design software.

This is a common occurrence in the emergent design of computer languages themselves.

In this case, you still get tests, but you don't get the emergent design aspects of TDD.

Chapters 10, 11, and 12 cover higher-level design concepts: classes, systems, and emergent design.