{
  "id": 12471051,
  "title": "Fix It in the Model or Fix It in the Source?",
  "url": "https://urgent.news/2026/10/06/fix-it-in-the-model-or-fix-it-in-the-source",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-06T21:21:22.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/jay_krshn_1a9ac493fadf8/fix-it-in-the-model-or-fix-it-in-the-source-2nha"
  },
  "original_language": "en",
  "account": "Deciding whether to fix issues in the model or the generated source is a crucial choice for teams working with CA 2E programs. The two options each have their advantages and disadvantages, but ultimately the decision should be based on where the program will be maintained in the future. The model should be considered the source of truth, while the generated source should only be edited for temporary experiments. When a fix is made in the model, it will be preserved in every future generation and provide an accurate description of the program. However, this approach may require someone who is familiar with the model's editors and can lead to wider consequences if the change affects multiple functions. On the other hand, editing the generated source is faster and more accessible to those familiar with RPG, but the changes will be lost when the function is regenerated, and the model will describe a program that no longer exists. To ensure that the model remains the master, it is recommended to make most fixes in the model and only edit the generated source for experiments or specific cases. When a fix is made in the generated source, it should be clearly commented and documented in a ledger, including information about where the values come from. This approach allows for transparency and traceability, making it easier to identify and address any issues that may arise in the future. In conclusion, deciding whether to fix issues in the model or the generated source depends on the specific needs and maintenance requirements of the program. By understanding the implications of each option and making an informed decision, teams can ensure that their CA 2E programs remain accurate, maintainable, and up-to-date.",
  "summary": "Fix It in the Model or Fix It in the Source? The first compile error in a converted CA 2E program forces a decision most teams never make on purpose: which copy is the master now Getting a CA 2E-generated program to compile is mostly mechanical. Article 7 covers the four causes that account for almost all of the errors. But every fix you make raises a question the compile listing never asks:…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}