<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-S7AOPxqbVXtQ2Pdl57QbZw" name="new_concept,_5xecwMXeEe6PpZUqNEM0jA" guid="-S7AOPxqbVXtQ2Pdl57QbZw" changeDate="2024-02-07T10:07:37.427-0800">
  <mainDescription>Refactor mercilessly to keep the design simple as you go and to avoid needless clutter and complexity. Keep your code clean&#xD;
and concise so it is easier to understand, modify, and extend. Make sure everything is expressed once and only once. In the&#xD;
end it takes less time to produce a system that is well groomed. There is a certain amount of Zen to refactoring. It is&#xD;
hard at first because you must be able to let go of that perfect design you have. envisioned and accept the design that was&#xD;
serendipitously discovered for you by refactoring. You must realize that the design you envisioned was a good guide post,&#xD;
but is now obsolete. A caterpillar is perfectly designed to eat vast amounts of foliage but he can't find a mate, he must&#xD;
refactor himself into a butterfly before he is designed to search the sky for others of his own kind. Let go of your&#xD;
notions of what the system should or should not be and try to see the the new design as it emerges before you.</mainDescription>
</org.eclipse.epf.uma:ContentDescription>
