Full-Stack because I like to do frontend and backend

Full-stack, because I know javascript.

Full stack but now i want to focus on the backend.

What is full-stack?

@STRINIX knows frontend and backend. i.e can code HTML and css and knows PHP.

@saiphp with knowing frontend I assume you also mean theories and rules and stuff when it comes to design

Yo momma loves my backend work.

@d4ng3r0u5 underrated comment here ladies and gentlemen

@STRINIX no, that's ux/ui. They tell us where to put it, we put it there. Ultimately you build enough site/applications you develop a basic understanding for optimal layout flow, but it's not a requirement of a Front-end developer.

As for full stack, these days just knowing javascript with html and css is enough to be considered full stack.

Mongo JS database
Node JS backend
Express JS api

So while my contract says Front-end developer, our technical leads wants it changed to web application or javascript as Front-end technically is html, css. And basic javascript. Once you move on to web/single page applications, you are far beyond the technical definition of Front-end.

Hek, I build a mobile application using javascript.

Currently I'm mostly working on the backend and sometimes I feel like are frontend devs have no fucking idea of what they are actually doing. The UX is horrible af and so much just does not make any sense (UI flow etc.).
And the code style.....I don't even want to begin talking about this.

Full stack is not knowing some backend tech and JavaScript...

Full stack is being all around. From setting up the server and it's services, to developing the backend and frontend, but also designing the database and it's maintenance.

It's a role for a person to know about the full stack, so usually the role is mainly used to serve as a bridge between the different devs/teams for full architecture debugging and planning.