This "who you know" type of thinking might work in the short term, but in the long term it will bite you on the ass real bad if you don't also have "what you know".
My ex girlfriend was like that. Flunked everything she studied, got by on her personal connections, etc. Ironically, one day I introduced her to a buddy of mine I'd studied with who worked for a big government organisation. She used that connection to get a job there, then bluffed her way into a position earning double what I did at the time. Then she dumped me. So far so good. Problem is the job was *way* above her skill level. I warned her when she applied, but she ignored me and said she would learn on the job. OK, lets see how far this goes. At first she watched her colleagues and imitated them. If she got stuck she would ask one of her many friends to help or advise her, maybe under the guise of needing a "second opinion" or something. She had to rotate this task between friends often so her incompetence wouldn't become too obvious. If anyone ever made an issue of it, she would find excuses. If she fucked up, she would conceal it. This seems to work for a few years.
Eventually, one by one, her friends became fed up with covering for her. They had their own jobs to do. This is about the time when she really fucked up big time. She tried to cover it up of course. Unfortunately for her the customer got a layer, who then asked her top boss for compensation. This triggered an internal investigation which revealed she had covered up multiple big fuck-ups. She got the boot of course, plus a court case which dragged on for over a year, plus her name all over the newspapers and the internet. Now, every single time a prospective employer Googles her name, they get a screen full of bad press, and her CV is filed in the bin. Anyone stupid enough to vouch for her will be tarnished. I think she ended up giving "happy massages" to make ends meet. As far as I know she is still unemployed several years later.
If you thing you can get by with "who you know", and not "what you know", then you are a fool. Good luck to you. Just remember, eventually your reputation will catch up with you. When it does, who you know might not want to know you.
The beauty of SQL is the way it lets you specify *what* to get, not *how* to get it. It frees you from the implementation details. To understand why that is so important you should read the article A Relational Model of Data for Large Shared Data Banks by E. F. Codd. Written about 45 years ago, but still remarkably readable and relevant. The relational model has a very elegant mathematical foundation that ensures data integrity. No other data model before or since comes close to matching it. SQL tries to implement the relational model. One benefit, every SQL query produces a relation, which can itself be queried (subqueries).
Having said that, I work with SAS every day, which basically buffers one record at a time and does whatever I tell it, however I tell it.
xkcd to the rescue again. Try this:
makepassphrase()
{
return 4;
}
Doesn't help when software overuses such an annoying feature. A teacher at university actually insisted we respond to every user action with a popup acknowledging the action. User saves a file. Popup: "File saved". Well thank fuck you told me, because there is no way I would have noticed pressing the save button if you hadn't blocked me from doing my thing to show a popup! Or even worse: "Are you sure you want to action X?" where X is benign and completely reversable. Of course I fucking want to do X, I just told you I want to do X, why won't you do X already! I tried to explain to my teacher how I stop reading popups after the second one and how other people probably do the same, so it's better to use context based feedback. Disable the save button or something until there are changes to save again. Use popups only when it's absolutely critical to do so. But no, popups for everything. I see commercial software use this same braindead design. Needless to say, I ignore everything the software tells me, even the critical stuff.
In the backup scenario you present the users don't care. They pay someone else to care. But if shit hits the fan and they need a recovery, they will demand blood if they don't get what they paid for. Best to send warnings somewhere else instead.
An Ada exception is when a routine gets in trouble and says 'Beam me up, Scotty'.