Maybe it was a quirk of my personality or maybe just the kinds of jobs I wandered into, but I've long believed there is a certain -- well, almost a nobility -- to making infrastructure supportive but invisible.
I believe there are two aspects to that. One is design, which creates an object or experience that just works. It's one reason I've "paid the Apple tax" in buying computers and smartphones over the years. It's why I love my ASKO dishwasher, which is simple to use, built like a tank, and swallows everything that should be washed in a dishwasher and cleans and dries it using less water than I would washing by hand. I had to dig deeper into the budget to buy it. But it's been worth every penny to me.
The other aspect is process. The people at your favorite store who anticipate your purchase by making sure there's a variety of sizes/colors on the shelf -- or even that the shelf is stocked before it's absolutly empty, by an employee who does not block the entire aisle with their cart -- that's process. For many years I worked in computer operations, "keeping the training running". There was a lot of work done analyzing traffic to help ensure that, when a bunch of users were added to a system, it didn't bog down into unusability. Or to make sure that Wi-Fi throughout the building was fast enough and generally available, not spotty or sporadic.
People tend not to notice when things work -- but they surely notice when they don't. That does not typically happen by accident. There are entire fields of work involved in making sure things work. Maybe calling it "love" is extreme. But people who don't like people generally don't create things that just work. Now, the environment in which that happens? That's a different deal.