Combined Rules of Agile Process

I would like to propose a new and perspective approach to an Agile development.

The central concept of Agile development is TABCAGIANA - Take Any Banal Concept And Give It A Nice Abbreviation. 

The most clear and simple way to be an agile programmer is to invent and use such abbreviations whenever possible.
The major flaw in modern programming is that there are no widely adopted and, more important, properly abbreviated patterns for creating agile abbreviations. So people tend to name their rules without a particular system.

I want to propose my own set of agile principles, which where, on contrare, created with a single approach in mind. They're called
Combined Rules of Agile Process (CRAP). I call them "combined" because they target two issues simultaneously: 

1. By following those principles constantly, you'll become a better developer.


2. By extensive use of corresponding abbreviations, you'll give your site a surprisingly larger audience.

Here are the principles (first one  wasn't invented by me):

• Keep It Simple, Stupid 
  
• Follow Universal Conventions, Kid
  
• Premature Optimisation Reproduces Nonsense
  
• No Unambiguous Design Exists
• No Actor Knows Every Detail
  
• Pragmatic Architecture Results In Scalability
• 
  

So everyone is welcome to use this extremelly Agile and usefull abbreviations in their publications and also to invent their own, following CRAP approach.
Good luck!

P.S. DROP EVIL PLEASE

DRY -Don't Repeat Yourself - is another well-known agile development principle. And probably the most repeated one.
I would like to introduce another concept.
It is called DROP EVIL - Don't Repeat Other Persons, Even Very Intelligent and Lovely.
PLEASE - Peolpe's Language is Expressive and Aesthetic, So Enjoy.