1. If it is mentioned in the requirements, it will not comply the architecture.
Corollary: If it is developed as per the architecture, it will violate the requirements.
2. If it is developed quickly, it will come back, after review from onsite.
Corollary: If it is developed gradually, then also it will come back after the review from onsite.
3. If you try to understand the architecture, you are bound to fail.
4. If you try to do a simple code process/activity , as per your understanding, the code will work[But architecture will deny that approach].
5. Architecture is a mystery, an everlasting puzzle, never disclosed to developers, except used in bits and pieces to rebuke developers, every now and then, especially when they are running short of time.
6. If something is working fine in local DEV environment, it will fail in MML DEV.
7. If something is working fine in the MML DEV, it will fail in the BETA environment.
8. If a code is successful in the BETA, it is not the latest code.
Corollary :If a code moves to the production it will produce 100000 errors in a minute.9. If you have not used the latest code, your development will be fast.
Corollary: When you will be running short of time, a new code will appear.10. When you will be free, with a lot of colleagues, testers and developers, nobody will call from onsite.
Corollary: If you are about to leave, testers are not available, you will get a call and would be asked to test your code.
11. If a code has been reviewed by onsite, developed again; architecture team will ask for further mends.
Corollary: Architecture team will change the code to the one which was working before the review from onsite.
12. If it is a big change in the code, you will be asked, over the phone, to do it, just before the half an hour of deployment of the code.
Corollary: If it is a small change, then also the code will come back, with a big mail addressing the blunders.
13. All the meetings seem the final and critical ones; none of them ever are.
14. Profound changes are often talked about but never take place.
15. If you discover that you are delivering as per an informal ‘change request’; you will have to make the changes.
Corollary: If you do not discover that it is a ‘change request’, you will do so later on.16. If you have developed the code to produce an output, which is similar to the production output; production files will be wrong.
Corollary: If production files aren’t wrong, you are required to develop as per the mapping document.17. If you have followed the mapping document, you will find that it isn’t compatible with the production output file.
18. Production output file is never compatible with sample output file.
19. If it is a change suggested in the code-walkthrough, it won’t be present in the requirements document.
Corollary: If it is not suggested in the requirements document; it will be suggested in the code walkthrough.
20. If you have not got a latest code today, it should be a holiday.
[ Vice versa is not true: If it is a holiday, then also you may get a new code to be used in the development]
21. If an interface seems simple during the development, it will, undergo many changes.
Corollary: If an interface looks complex during the development, it will undergo many more changes after the development and development will be way too short of meeting the deadlines.