There's a reason pretty the majority of electronic addressing uses that second format***. It's just easier to follow, and in fact you can start executing before the sentence is finished - as well as discard any specifics you don't care about without having to scan the entirety first.
Following the second instructions works like this: Go to refrigerator, go to second shelf, go to back right, go to jar.
Meanwhile following the first set of instructions requires this: remember jar, remember back right, remember second shelf, go to refrigerator, recall second shelf, recall back right, recall jar.
It is objectively a worse way to give instructions, because you are giving them in reverse order.
If you had to code some software following instructions and your interface was push(instruction)/end(), your first sentence would require more code and more working memory just to store instructions until you've given the last one, while for your second example they could just be executed right away.
*** Funnily enough it still tends to get flipped the closer we get to natural language. URL paths, domains, IP-addresses, etc, are all written the proper way, except if you add usernames into the mix. Suddenly we turn natural language "at" into "@" and prepend them.
For most purposes the second format is superior for the very reasons you state. In a certain world it's always going to be superior.
However, it means that concepts which are not attached to a worldview become harder to work with. Think of making subassemblies of jigsaw puzzle pieces. You can see that pieces are related and fit together without knowing what you're actually looking at.
Following the second instructions works like this: Go to refrigerator, go to second shelf, go to back right, go to jar.
Meanwhile following the first set of instructions requires this: remember jar, remember back right, remember second shelf, go to refrigerator, recall second shelf, recall back right, recall jar.
It is objectively a worse way to give instructions, because you are giving them in reverse order.
If you had to code some software following instructions and your interface was push(instruction)/end(), your first sentence would require more code and more working memory just to store instructions until you've given the last one, while for your second example they could just be executed right away.
*** Funnily enough it still tends to get flipped the closer we get to natural language. URL paths, domains, IP-addresses, etc, are all written the proper way, except if you add usernames into the mix. Suddenly we turn natural language "at" into "@" and prepend them.