This again. Is a doctor in his first year of being a full fledged doctor any less of a doctor than one with 20 years of experience? The more experienced doctor is almost assuredly better and preferable, but both of them are doctors. This assumption that you have to be a master of the front end and a master of the back end to be a full stack developer is flawed from the start. Have you created economic value with a co…
The Myth of the Full Stack Developer
81–90 of 104 posts
Re: The Myth of the Full Stack Developer
#82How ironic that I get an "Error establishing a database connection" error.
Re: The Myth of the Full Stack Developer
#83>"most “full stack” developers have not truly mastered front end and back end" We need to do something about the default of developer bashing prevalent in our culture. There's no true Scotsman, nobody is 100% perfectly attuned to the latest developments on any surface. Instead engineers develop along competencies that are required in their work. If you need to deep dive into a backend problem, you'll get better at th…
Came to say the same. I've seen good developers that are working on front-end, back-end, and full-stack. The key is that they are a good developer. Where they focus usually has more to do with the organizational structure and its values than the engineer. If they are the best in their area, if you move them, they quickly become the best in that area. Besides when back-end means you work on a web API and frontend mean…
It depends on what's behind the web API, doesn't it? Maybe there's a stock exchange back there.
Re: The Myth of the Full Stack Developer
#84My title is "full-stack developer". Does that means that I'm the perfect developer? That I am senior is all the technologies that I touch? No. It simply means that I aim to learn all parts of our stack and do my best to master them. It's not a chore to me. I don't have to kick myself to keep up with design trends and programming trends. I love both of those fields and can't even imagine not keeping up with both side…
Ding! That's what we are, we're like outfielders in Baseball. You need great pitchers and catchers buy it's hard to win a game without good outfielders.
Re: The Myth of the Full Stack Developer
#85>"most “full stack” developers have not truly mastered front end and back end" We need to do something about the default of developer bashing prevalent in our culture. There's no true Scotsman, nobody is 100% perfectly attuned to the latest developments on any surface. Instead engineers develop along competencies that are required in their work. If you need to deep dive into a backend problem, you'll get better at th…
Came to say the same. I've seen good developers that are working on front-end, back-end, and full-stack. The key is that they are a good developer. Where they focus usually has more to do with the organizational structure and its values than the engineer. If they are the best in their area, if you move them, they quickly become the best in that area. Besides when back-end means you work on a web API and frontend mean…
Re: The Myth of the Full Stack Developer
#86The reality is a really experienced dev is not really going to be all that much more productive than a well-managed and mentored junior dev. Sure, there are 10x devs, but really, sheer coding productivity isn't worth as much as it used to be. The 10x dev is going to quickly run out of things to do in most shops.
So what you have here is that sure, a junior dev can be a full-stack dev. He's dividing all his attention between all areas of the stack. He's not massively productive in any of those areas, but he's a hammer you can throw at software issues and be able to expect resolution.
That's what businesses need. Developers that can work on teams. You need just enough experience on the team to where problems one dev can't fix efficiently can be escalated to a senior dev, but there's no need for anyone to 'master' anything. Technology just doesn't work that way. You build your experience as you progress through your career, and you're always learning something new.
In fact, junior guys can be way more productive than senior devs. While the senior devs are thinking heavily about architecture, (while playing ping pong) the juniors are knocking out tickets.
Re: The Myth of the Full Stack Developer
#87"Full stack developer" is just a new word for "programmer". "Programmer" could be a role for any part of the stack, you just have to solve the problem in hand and you're good. If you're good or not, specialist or generalist, that's another discussion.
It would depend on who you ask but I consider that to be truly full-stack you need to be able to work on the UI/UX and design. With that distinction, full-stack isn't a new word for programmer.
Re: The Myth of the Full Stack Developer
#88I've come to the conclusion that the only 'real' "Full Stack Developer" is one who, indeed, knows what the stack is, and how to use it. Also, the heap. Think about it - those who don't know these things, and don't care - usually gravitate around a singular technology that lets them ignore the details. Those who do know these things, and how to use them properly, usually don't have any particular focal gravity, and ar…
PUSH POP PUSH PUSH PUSH POP POP POP ...
Re: The Myth of the Full Stack Developer
#89I've come to the conclusion that the only 'real' "Full Stack Developer" is one who, indeed, knows what the stack is, and how to use it. Also, the heap. Think about it - those who don't know these things, and don't care - usually gravitate around a singular technology that lets them ignore the details. Those who do know these things, and how to use them properly, usually don't have any particular focal gravity, and ar…
I am a millenial and i like your comment, although of course the "stack" that the article mentions has nothing to do with the "stack" you are referring to... PUSH POP PUSH PUSH PUSH POP POP POP ...
And I'm not surprised it hasn't gone well with this crowd, because - after all - "who needs to know what the stack is, amiright?", kids?
Re: The Myth of the Full Stack Developer
#90I've come to the conclusion that the only 'real' "Full Stack Developer" is one who, indeed, knows what the stack is, and how to use it. Also, the heap. Think about it - those who don't know these things, and don't care - usually gravitate around a singular technology that lets them ignore the details. Those who do know these things, and how to use them properly, usually don't have any particular focal gravity, and ar…
> millennial developers somebody is racist! then again, your comment really doesn't affect me. i'm millennial and i build web applications for a living. i also hack on operating systems and hardware in my spare time. a lot of my peers do the same. it really doesn't have anything to do with the generation you belong to. some people are shit developers some actually care about the craft.
Except, there really isn't. You still need to pay attention to the state of the stack, whether its the memory kind, or HipNewTechDeJeur™ kind.
I don't think a lot of new developers learn these things, though. Or else there really wouldn't be a need to describe "full stack developers". In the good ol' days, it was pretty important to know the context of your heap/stack usage - it still is.
(That's the point.)