I have been working with some validation code for a UI. One of the entry fields is a year so I added a range constraint to enforce a minimum. For purposes of this example assume it is a year of birth. Given that the oldest person alive is 118 it is fairly safe to assume that all dates of birth will be in the last 130 years.
Given that it is now 2022 this means that the value needs to be in the range 1892-2022. Enforce this too strictly and if you enter 0 and tab away the field defaults to 1892. This now becomes hard to edit as each time you change a digit the validation will restore the minimum value making this field really hard to edit. All you can do to make this easier is to warn that it is out of range.
Yesterday the British government held a mini-budget that made major changes to policy. Reducing taxes while increasing spending requires borrowing. Doing so on the edge of a recession is an interesting approach.
In the analysis of the budget there was a lot of discussion about the lack of growth in the UK economy over the last few years. Growth must be relative to our neighbours so that rules out Covid as a reason? What remains does not seem to be talked about. The reason why we have the economic mess is the act of economic self-sabotage that is Brexit. Why is no one calling this out.
The ERG seems to have taken over the conservative party. The 40 odd members of this secret society (the membership list is available but not published) have a controlling interest. They have more than half the parties majority.
Where is the balancing group or moderates? Have we no-one ready to challenge them from within their own party?
The book “Generative Programming Methods Tools and Applications” was published in 2000. It made the hypothesis that software would follow the same pattern that car manufacturing does.
In the highly automated car production pipeline it is possible to order a highly customised car yet have it built on a stardard production line from standard parts. GP:MTA assumed that this would soon be possible in software.
Dollard 2005 [Code Generation in dotnet] provides some univetsal priniples for code generation that apply irrespective of the implementation language.
We now have the Wonder articles (phase I) but the process stalled there. Dollard 2005 gives the techniques needed. See github.com/chriseyre2000/perfectstorm for an old but distinct implementation of Dollards ideas.
These techniques did not get the required level of adoption so that reusable templates could be produced. This was left at the initial stages of evolution.
In order to be taken further it will require some big adoption that makes it to a confrence paper. This could bootstrap the reusable catalog idea.
Code generation like this is not a 4GL, merely a means of extracting the business details from the implementation technology. You can achieve reuse without using up key options (single inheretence languages can avoid using up this powerful tool).
Try to keep the logs quiet. If something is happening we need to know. Logs can tell you that things are happening or have gone wrong. A request for intervention should be made once, pteferably by opening an alert on OpsGenie
Try to keep error messages clean. If possible treat warnings as errors. Noisy compile messages will hide real errors.