We will see how this goes. But, for now the 5 rules for quality for me stand even today are:
– Deliver an artifact and ensure no one can find a defect;
– I can refactor the code knowing it won’t break anything;
– Code commits work like a charm and i can deliver code in environments quickly and with certainly;
– When I send this application to my dear friends in operation, they don’t hate and curse me;
– Quality meant, once my work is done it’s done
Use Annotations to anything is is core to the application and defines the core structure of the application. Anything that would need a code change is okay to sit as an annotation. Rest everything else should be XML.
To sum it up in plain english – Not a lot of rope to hang off of; very little use cases to use and not exciting me as much.
For anything that is enterprise or platform(ish), I won’t go for this. The technical overhead that this framework and what it solves for is not worth the ROI of managing another framework. If I’d come across strongly types content-types, I would consider to use this. The ultimate tie breaker would be how how many of the content-types need to be displayed “as-is”. If all i had to show are several compositions of data (search or what have you) maybe not. But, definitely something to consider
Project start is the time when is most critical and single-handedly decide the fate of the project. That is the time when we are preparing ourselves for a journey, and how well prepared decides: When we reach out destination – on time or late In what condition we reach – as expected or all burnt