|
|
|
|
|
by swframe2
1562 days ago
|
|
1) don't learn from your mistakes; learn not to make mistakes.
Look at what others have done; there are a lot of blogs about what when wrong with similar products; make sure you don't repeat other people's mistakes.
Take a hard and deep look at the failures to identify and fix the structural reasons they happen 2) increase the effort you spend on tests;
write less code; implement simpler features; code review every change.
Don't listen to anyone who tells you it is ok to test less; do what will make the company the most money long term; it is better to work somewhere else than to work for someone who doesn't care about product quality. Alpha/Beta test more. 3) implement a checkpoint/rollback system (using git can save you effort)
Save config changes to a temp location so it is never lost.
Allow test configs to be validated and then allow the user to roll out the new config gradually.
Save the old config so users can rollback easily.
Implement a monitoring system that can auto detect failed rollouts and trigger rollbacks. |
|