you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 day ago* (2 children)

I've pondered on the feasibility of using codegen to manage projects done by codegen and the problem I see with that is that regenerating a project just replaces known bugs with unknown bugs rather than actually fixing bugs, plus the user interface will also change even if the requirements specification is so complete and well done that it manages to have the same features, and user really dislike that plus there are actual costs in retraining people to use a whole new UI.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 23 hours ago (1 child)

    I agree. Although I've been thinking more along the lines of bug fixing, adding features, and incrementally changing said app. So like you would with a human team, disallow large-scale refactors as a rule. As far as I can tell, that relies on codegen to be well-skilled and well-behaved - a whole other area that requires labor with possibly diminishing returns.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 22 hours ago

    To fix the bugs with targeted regeneration, you have first to find where there bugs are, meaning incurring the cost of understanding the generated code.

    By the time you track down were the bug is you might as well just fix it by hand yourself.

  • source
  • parent