Irony With Code Genertaion Techniques & Research

Irony With Code Genertaion Techniques & Research

1.  Code Generation only matters in the Agile-EA-SPLE context. But Code Generation Techniques have been purposed in wrong context or with not context.

2.  Development techniques have been purposed with only Code Generation focus, it says nothing about the Context, or they are purposed in some Lab Context or Demo Context or Class Room Context. Things Development in wrong Context and Lessons learned from that Wrong Context are eventually wrong. The Experimental Settings should have to be real only then the results are valid, applicable and true.  

3.  Only by seeing the repetition in EA development, many techniques have been purposed without caring about the Context in which Code Generation matters.

4.  These techniques purpose Modeling Languages and generate Fully Running Demo-ware or CRUD Application. Such techniques cannot be used practically in EA Development. These techniques are misfit in the practical EA development and do not give the Code Generation Benefits.

5.  Many techniques have been purposed without context, they claim to support any type of Software Development. It matters only in EA-SPLE-Agile context.

6.  Code Generation is supporting actor, it is secondary actor and can works well only if the EA-SPLE-Agile context is there. EA-SPLE-Agile should have a Prime Focus; only then Code Generation can give benefits. If the EA-SPLE-Agile is not there in the Context, Code Generation is a waste, burden and recipe for failure.

7.  EA-SPLE-Agile can work without Code Generation. Code generation can be helpful in EA-SPLE-Agile. It an option. It is not mandatory.

8.  Without EA-SPLE-Agile, Code Generation has no scope and cannot be applicable. EA-SPLE-Agile can be done without Code Generation.

9.  If (EA & SPLE & Agile) Then  (Code Generation)

Else (No Code Generation)