78 AnswersNew Answer
@Ramalingham... I think what makes the backend so appealing to so many developers is it allows you to focus on the logical abstractions of an application isolated from the concerns of the presentation layer. There is something pure and satisfying about refining abstractions to be more efficient, organized, reusable, and capable. For many developers, this is their place of Zen where they can get into a distraction-free zone until they reach a point where their fingers, typing on the keyboard, can't keep up with the flow of logic and layers of abstractions manifesting in their minds. Once you reach that state of productivity, it's like you've entered into a trance, staring deep into your monitor(s) and those around are in awe, as they bear witness to your fingers tearing up your keyboard and your screens flickering with controlled chaos. The code files switch around on the screen so quickly as new lines of code appear like magic before switching to another file almost instantly where new code emerges without pause. As this moment of intense focus and clarity is sustained for hours on end, the result of what appears to be a virtual choreography of dancing code, becomes your "piece de resistance". And for that moment, you are at peace... Until you realize you must wrote a ton of crap and need to scrap the entire thing. (j/k 🤣) But seriously, for me, I love being in this mode. It's much harder for me to get lost in the zone when doing frontend development. Occasionally, I'll hit brief moments like this on web development. But it's short lived and momentum is reset. Still yet, the reward for frontend can be just as satisfying, but in a much different and slower way (for me at least).
I am also a full stack developer, but I prefer to work on back-end.
I've been a full stack dev for a long time but I'm happiest when working on back-end.
Facebook is so powerful due to the gigantic data in back end servers. Although what users perceive are the front end web cosmetic presentation, what really support Facebook running their business is the back-end architecture, which they spent billions of dollar per month to run it. If you want to build a powerful website or web applications, make sure your teams have good skill in back-end technology.
you can learn both. as a full stack, i do front end, back end, it, ui/ux, etc. there is nothing wrong with learning as much or as little of the other areas as you want.
I find it's best to know a little of the other (like know a little front end if you work back end) as it helps when collaborating with a team.
This is a clarification response for several questions posted throughout this thread: Frontend: - Refers to the part of an application with a Graphical User Interface (GUI or UI). - This can also be referred to as the presentation layer or a client app that interfaces with a "backend" server. - Frontend development can involve applying the visual design, layout, and styling, the user experience, navigation flow, communication with the backend server, various client side functionality, etc. - Frontends are not languages specific. They can apply to the web stack (HTML/CSS/JS), mobile apps, desktop apps, etc. Backend: - Refers to one or more remote middleware services or server processes that typically sits between the frontend application and a central database. - This can also be referred to as the middle or business layer. - The "backend" architecture can be as simple as a basic RESTful API / WebService or as complex as a series of micro-services, SOA services, orchestrated via a services bus, message queues, or any number of other architectural paradigms. - The "backend" can be used by multiple "frontend" clients. This allows for apps to be written for web, Android, iOS, MacOS, Windows, etc. - Common tech stacks used for the "backend" include Java, .NET, NodeJS, Ruby, Python, Perl, and others. - Although the database layer is an independent separation of concern and considered its own layer, many people include database as part of working in the "backend". However, this could be different from project to project. Fullstack: - Refers to a developer with diverse enough skills to be proficient with both frontend and backend development.
I've been a full stack developer across multiple platforms and OSs for quite a few years. I started out heavy in server side (a.k.a. backend) development and eventually crossed over to heavy UI frontend a few years later. For me, I'm much more at home with the backend development. However, I really enjoy doing frontend development. It's like visiting a second home. I wish I spent more time there, but I'm very comfortable with both.
so what if i just learn both? like im primarily focusing on front now but i want to be the best out there someday. i code(learn myself) 8-9 hours most days because its all i want to do. ever.
First I will go with front end part then I'll with Back end
@ David Carroll I was giving a french class once. The students were asked to describe the actions depicted in various pictures. One showed a couple kissing on the street. In french, the verb " baiser " means to F***, but the noun " un baiser " means a kiss. My student understandably but erroneously infered from what she knew and came up with the caption " L'homme baise la femme dans la rue " = The man is f****** the woman in the street. It made my day.
fullstack making frontend and backend during creating web-sites
use react for front end and php yii or laravel for backend
yes it depends on the company but companies are crazy of React.js frontend and backend with php yii framework if you have no idea about React so check my simple react code youll get the magic of React....
I love back end but I love front end more. Cause most clients have little o no knowledge of programming. So what the appreciate most is the look of the site o program.
I'm a beginner full-stack and middle frontend. And like frontend very much) Backend is not interesting and more difficult as for me
js is frontend
definitely the back end.
to be a good web developer, at least you have to know a little of the opposite area that it works for, I think to interpret the output of your code in the backend, you should interpret the input of the frontend code, and vice versa, thus making a dynamic code and easy to work in conjuto!