Some things will outlast your lifetime. COBOL banking systems are still undergoing active maintenance, and the aircraft reservation systems are stuck in the 60s/70s. Unmanned sacecraft can operate for decades and the hardware, at least, is not replaceable.
The trick is to figure out the non-obvious criteria that cause the thing you're working on to fall into one of the other bucket. Nobody thought the banking systems would last so long (else there wouldn't have been a Y2K crunch). And some of those quick-and-dirty business systems stick around forever.
Non-programmers could learn, understand and use SQL for their need.
So, i migrated from a RoR stack, which uses Active Record into the SQL to API approach. That means, i put non-programmers into the center of my stack.
That said, developers will need to build more strong abstraction, so that non-programmers could stand on their own to build their things. It's not the job of developers.
Developers is to build foundation.
What i mean is, if i would be not the maintainer of my projects later on, i don't need developers to maintain (and maybe adding features), because non-programmers could use SQL to build their stuffs.
So, the less code for logic, the better.
I'm incredible tired of this productivity phrase being thrown around at whim. These claims are rarely verified.