I'm a self-educated, tenderfoot ish coder, so I am sorry on the off chance that I don't nail the developer language.
I'm dealing with a task in which I am giving information, which will be ceaselessly refreshed, to engineers who will basically make an apparatus to produce reports from questions on the information. It appears that everybody included believes that they have to hard-code information esteems (not simply the blueprint, yet the spaces/values) into the report-age program.
For instance, assume we were providing details regarding staff; the report would be part into classes, with a heading for every office, and afterward under every office heading will be subheadings of occupation titles, and after that under every subheading will be a rundown of workers. The engineers need to hard-code the divisions and employment titles. Then again, I would feel that they could/would inquiry out those things at runtime, sort records by them, and create report headers powerfully dependent on what esteems are there.
Since the rundown of potential qualities will change after some time (e.g., divisions will be made/renamed, new occupation titles will be included), the code should be persistently refreshed. I can't help thinking that we could skirt the code upkeep steps and powerfully sort out the reports.