When can you say "I am full-stack developer"?

Question

This is a buzzing word in industry, and a lot of people are using this word. So what makes someone actually a full-stack developer. How much front-end and back-end should you know before you can call yourself a Full-Stack developer?

Answer 1

Before I can call myself a full stack developer, I must learn to create projects from scratch to production level and also it has to be timely, along the journey of this road, I will surely meet errors and bugs, so before I could say I am a full stack developer, I should be able to patch bugs and fix errors, finally, I should be ready to work with any framework clients or co-developers bring up to achieve end goals.

Answer 2

The issue with the "Full Stack" of a Web Developer is that it is indeed FULL, yet, they are layered on top of one another as in a stack..., making it easy for newbies to pick the necessities one after another...

This list below would make an industry-standard Full Stack Web Developer:

Languages
• HTML
• CSS
• JavaScript
• MySQL
• PHP

Frameworks / Libraries
• Bootstrap (or Foundation)
• jQuery
• Ajax

Concepts
• Responsive Web Design
• Design Patterns
• Object-Oriented Programming
• Web Performance
• Testing
• Debugging
• Validation

Soft Skills
~ Agile Development
~ Teamwork
~ Communication
~ Teachability
~ Self-Motivation

[I'm actually "becoming" a Full Stack Web Developer]

^^-^^

Answer 3

For front-end, I'd say when you know HTML5 and CSS3😜. For back-end there are a lot of good choices. I don't know a lot about back-end so I'm not going to say much about it.
You should know your way around a lot of frameworks and have an idea about how to use them properly and the trade-offs of one framework over another. I think that applies to both front-end and back-end. Knowing a lot of frameworks doesn't mean being a jack-of-all-trades, it means you can learn and use different frameworks for different tasks. Being good at design, and making something that the user finds easy to use. Having good problem-solving skills means you can solve real-world problems. Also agree with @Awele, also need to be able to fix bugs and errors.

Answer 4

The sad life of a programmer is the burden that he/she will be learning the rest of his/her professional life. It never stops and I know what I am talking about.

Answer 5

@Leon: You should be careful not to overdose yourself. You only need to learn what you actually frequently need to use. But I know a lot of our peers that have a big bragging problem. They know not even the basics, but just a few keywords that are involved in certain matters, but kind of keep repeating them so load and often, that the ones that don't have a clue believe they master all those things on a very professional expert level, what's not the case. No one, but no one can know everything and wouldn't even have the need for it. So stop bragging and aiming and get your feet back on the ground guys. There is still some life to live beyond programming, believe me freely because I have been on the other side with a real bad burn out.

Answer 6

The truth is, it depends. What it really means is that you are a developer who solves problems on the entire stack of a product. But stacks can involve any variation of a number of languages, systems and frameworks.

Typically a full stack developer will work on the frontend, the backend, the database, and the system it is all running on. In my job as fullstack dev, I work with Python, XSLT, HTML, JS and jQuery, Arch and CentOS linux, PostreSQL, Flask, and probably a bunch more that I'm forgetting to list.

Answer 7

I wasn't judging you Leon, I understand completely what you mean but I shouldn't have used the @ symbol this is what I automatically do when I respond to any thread. So don't take this personal at all. I meant actually the majority and specially you should understand where I am coming from, because like you said your self a lot of people complain or strive for complements while it is beside the issue. I loved and still love the continuing changing world of software development. I started in 1978 so that's a while ago. And step by step I expanded my horizon.
But there are still so many corners in software development that I never used nor will use, because I'm in a different field. That's all I wanted to point out. Many peers claim knowledge they never even seen closely... but hey Leon, don't over do it. Karma is a bitch, I know because it has bitten me very bad at some time. So take a wel deserved break once in a while to spend some quality time with your family. Success my friend 😆😆😆

Answer 8

when I learn all codes of languages and create a project than I say im a strick develoer

Answer 9

@Anatoli: I'm not trying to learn all the stuff I listed, I have already been working with most of those technologies for many years.

After reading what you wrote about "the sad life of a programmer", it almost sounds like you have the wrong job. You're right that working as a developer means dedicating a lot of free time to learning, and while that probably isn't for everyone, I personally thrive with it. And that's coming from a guy with a kid and a wife and a limited amount of free time to spend.

Answer 10

great question

Answer 11

Never