Here a few mention a MDD tool could be used to generate the back-end part in web development projectĪnd It can be a great help for database management or a quick and dirty generation for a prototype but that for the front-end part, I think it is a waste of time specially because they had the feeling they would need to end up modifying lots of the generated code in the end since since this kind of tool will never be as configurable than a HTML/JS project. (5 – Totally sure, 1 – No way I’m doing that) but we always learn more from the cricisms □ Q2 – If you were working in a software company, how likely is that you would choose to use some kind of code-generation tool in your next web development project ? There were also some (but fewer) positive comments like: I think this is the tendency of the future. (5 – Very satisfactory, 1 – Totally unacceptable)Īmong the most cited (negative) reasons we had: lots of installation problems (I had to let them work in pairs so make easier for them to have access to at least one machine were the tool was working smoothly), lack of optimization of the deployed application (quite noticeable for a small application like the one we were doing, probably more reasonable when we move to more complex ones), sudden crashes and corrupted projects, good for prototyping but unsure if the if the method scales, lack of documentation and difficult to customize the code. ![]() Q1 – How would you mark the experience of using the code-generation tool? We already know that MDD pays off in the mid-term so they lack that long-term perspective when evaluating the experience
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |