anchor.diff:  
   This means that your users can fine tune the score function at runtime,
   by looking at the result of the `Solver`, changing the score function and solving it again.
  -That enables them to evolve the business planning much faster.
  +Those faster iterations, enables them to evolve the business planning quicker.
  
positive.code: ----
  
  And of course, we build a web interface so the user can create/update/delete +FreePenalty+ records.
  So the user can use to gui to create these records:
  
  [source,txt]
  ----
  
negative.code: <iframe width="853" height="480" src="http://www.youtube.com/embed/K084NKRZqkg" frameborder="0" allowfullscreen></iframe>
  +++
  
  Note that a _decision table_ is more powerful then a _data driven DRL rule_: the user decides which conditions to apply.
  The other conditions are not even included (which is faster than checking them against default values).
  
  == Rule templates
  
  If _data driven DRL rules_ aren't powerful enough for you,
  but a _decision table_'s `xls` file sticks out like sore thumb in your UI,
  use Drools _rule templates_ with a custom UI.
  
  == Drools Workbench
  
  Workbench (formerly known as Guvnor) is a full blown web application to manage rules and workflows.
  Using a web interface, business users can create and edit rules, including the score rules used by OptaPlanner.
  
  This is a very interesting setup, which I 'll demonstrate in a future blog post.
  Meanwhile, for more information, see https://www.jboss.org/drools/documentation[the Drools documentation].
  