Code commands. Format just keeps what we already know.
Python, JavaScript, SQL - these are languages you write code in. They sound like different versions of the same thing, but each is actually cut out for a different conversation. Think about how you talk differently with your mother, with a client by email, and while filling out a bank form. The meaning stays the same, but the tone shifts depending on who you're talking to and why. Programming languages work on the same principle - you pick the one cut out for the conversation that needs to happen.
Specifically: when you order something online, the button you click is written in JavaScript and talks directly to what you see on screen. Calculating the final price might run through Python, doing the math behind the scenes. And finding your order in the store's system is a conversation SQL has with the database - a huge organized archive where SQL knows how to ask the exact question and get the exact answer.
Formats are a different story. They don't order anything, they just record facts. JSON and YAML store settings - things like what color the button is, or which email a notification should go to. CSV stores tables - the same as a list in Excel, just rows of names and numbers one under another. If you open such a file and see lines with colons and brackets, you're not looking at broken code. You're looking at a note, left calmly, for the program to read.
You don't need to remember the names. What matters is recognizing the difference when you meet it - one is an order, the other is a record.
I look at the system
Before I even understood what code was, I'd opened up hundreds of settings files. The first thing that calmed me down was exactly this distinction: a settings file doesn't think, doesn't decide, doesn't make logical mistakes. It just keeps. If something's wrong there, someone wrote it crooked - the system didn't blow up.
So when I'm building something and I see an error, my first question is: is this code that needs to think differently, or a data file where something's just written in the wrong place? The answer saves hours of confusion, because it points to the right person - and the right conversation.