anchor.diff:  
   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.
  +Due to its 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.
  
positive.code: certified it on a lot of environments (including Windows, IBM JDK, OSGi and other notorious technologies) and guess what - they found bugs (and still do on occasion).
  Meanwhile our Product Manager helped organizationally.
  We talked to customers and helped complex use cases succeed: all very satisfying.
  And I got to travel to interesting places around the globe, such as San Fransisco, Boston, Buenos Aires, London, Paris and Tokyo.
  
  Meanwhile, _our_ project also graduated from the Drools project to become a top-level project.
  So we had to http://www.optaplanner.org/community/droolsPlannerRenamed.html[rename] the project again, one last time (I promise), to OptaPlanner.
  
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).
  