the real story about "measuring" developer productivity - if anyone ever really truly wanted to know, would tag two things. The people measuring cannot define any reasonable sort of measurement, and two, most development is brand new - almost an art form. Rarely are developers given a tangible target or description of a target. years ago, I worked in a group (actually still do but 1/2 are gone now) developers. The development project started with the ubiquitous phrase - "how long?" to which the developers asked, "what is it you want?" This got an eye roll from product development, management and sales. After falling prey to guilt, the developers threw out estimates where upon they were told, "no, that's too long, it has to be ready for the xxx3 trade show." After the other people's delivery target went zooming by (after a lot of free OT), the entire engineering group were held accountable for missing "their" estimate. 6 months later, we had a number of cubicles open.... So, what's the benefit of "low-code" tools? It's called RAD, tosses something fast in front of the possible customer to figure out what the customer really wants.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.