Dayaan M. answered 18d
Bachelors in Computer Science and certified in responsive web design
The whole split comes down to one question: where does the code actually run?
Front end code runs on the visitor's own device, inside their browser. Back end code runs on a server you control, somewhere the visitor never sees.
It helps to follow a single page load from start to finish. You type an address and hit enter. Your browser sends a request across the internet to a server. That server runs back end code, which might look up a user account, pull rows out of a database, check whether you are allowed to see the page, and then package up a response. The response comes back as HTML, or more often these days as JSON data. Your browser receives it, draws it on the screen, and from that point forward the front end code is in charge of what happens as you scroll, type and click.
So the front end is HTML for structure, CSS for appearance, and JavaScript for behavior. It is every button, form, menu and animation the user touches directly.
The back end is a language such as Java, Python, C#, PHP or JavaScript running under Node, almost always paired with a database. It handles accounts and passwords, payments, permissions, sending email, and anything that has to stay true for every user at once.
Now here is the part that explains why the division exists at all, and it is worth more than the definitions. Anything on the front end belongs to the user. They can open developer tools, read every line of your JavaScript, change values and send whatever they like to your server. That means front end validation is a convenience, not a protection. If your signup form checks that a password is eight characters long in the browser, that is a kindness to honest users, and it stops nobody who is determined. The real check has to happen on the server, because the server is the only place you control. Once that idea clicks, most of the decisions about which side a feature belongs on answer themselves.
This also gives you a practical way to find bugs. Open the network tab in your browser and reproduce the problem. If nothing is sent and the page still misbehaves, the problem is in front end code. If a request goes out and the data that comes back is already wrong, the problem is in the back end. Knowing which half to search cuts the work roughly in half.
A developer comfortable on both sides is called full stack.
If you are deciding where to start learning, start with the front end. You change a line of CSS, refresh, and see the result immediately, and that fast feedback keeps the early weeks a lot less discouraging.