1,107
edits
Support/PlatformEngineering: Difference between revisions
Jump to navigation
Jump to search
→Evaluation
| Line 15: | Line 15: | ||
The evaluation criteria are as follows: | The evaluation criteria are as follows: | ||
* Is the new codebase easier to understand and develop further? That is, is it easier/more enjoyable for our webdevs to do their jobs? | * Is the new codebase easier to understand and develop further? That is, is it easier/more enjoyable for our webdevs to do their jobs? | ||
* Can we get more done in a release cycle? | * Can we get more done in a release cycle? | ||
* Is the new codebase more robust? | * Is the new codebase more robust? | ||
* Is the new codebase at least as performant as the old one? | * Is the new codebase at least as performant as the old one? | ||
I recommend undertaking at least two release cycles, before performing a formal evaluation. This is in conflict with the desire to move forward as quickly as possible with the eventual decision path, however it is important to make a good decision here, which I feel cannot be done with only a single cycle. The first new release after the upgrade will be testing a new development process. Doing anything for the first time will be slower and more awkward. | |||
= Option 1: continue with Tiki = | = Option 1: continue with Tiki = | ||