Ideas to blog

Capability vs Configuration

Capability is the functionality the system has available

Configuration is how the functionality can be used to meet a specific customer need

Easy configurability, code as modules

xx

Requirements that change how things work for very narrow scenarios Shotgun effect across the codebase, lots of little changes Over time, these become viral (and not in a good way)

Counter: adapt to the strengths of the software instead of trying to use the software in a way that it wasn’t designed e.g. using git as svn

yy

When the requirement says you should create a document every time a pattern is seen, but then you have thousands of patterns and thousands out outcomes and how do you match up the two to work out what needs to be done