anchor.diff:  But there were also many services missing before a Fortune 500 company would consider using it in mission critical software.
   *Technical excellence alone doesn't suffice.*
   
  -Red Hat doesn't just employee the core engineers of an open source project, such as Drools or OptaPlanner.
  +Red Hat doesn't just employ the core engineers of an open source project, such as Drools or OptaPlanner.
   It also builds out a dedicated QA team, support team, consultancy team, security team and productized build/documentation team.
   This enables customers to deploy our Open Source software in large scale production cases confidently.
   In 2013, we started this process, called productization.
  
positive.code: 
  Ironically, this was also the period when the project became successful:
  downloads took off, the forum became vibrant, I got to talk at more conferences and the first https://github.com/droolsjbpm/optaplanner/pulls?q=is%3Apr+is%3Aclosed[Pull Request] arrived.
  Due to it's success, more bugs surfaced - so I heavily invested in unit tests and integration tests.
  By the end of 2009 I also renamed the project to Drools Planner.
  
  Luckily Red Hat - sponsor of the Drools project - had noticed my steady stream of contributions.
  
negative.code: 
  == Proving a point
  
  After graduating in 2003, I worked 2 years as a Java consultant and then took a job as an academic researcher on multi-agent systems.
  Those were going to change the world. They didn't.
  One of my colleagues was working on optimizing a nurse rostering problem and presented his approach to our research group.
  His solution applied https://en.wikipedia.org/wiki/Tabu_search[Tabu Search] (an optimization algorithm invented in the '80s).
  