Exactly! Just what I was thinking ... couldn't have said it better.
Also, if you're a freelancer/contractor (not an employee), it can be very beneficial if you can work in both areas (frontend and backend) - you can take on complete projects where both a frontend and a backend need to be built.
Finally, the article starts with:
"You specialize in PHP, ... none of which are related to frontend"
What's funny here is, of course, that PHP started out as a language to build frontends - just cranking out HTML. Nowadays separating frontend and backend is in vogue (using SPAs and APIs) but it's not always the case that the backend and the frontend duties are so clearly separated.
One thing I'll grant the author though, the term "full stack dev" is overused, you're seeing it way too often. By the way, is this article irony maybe? i noticed just now that the author is labeling himself as "full stack developer" ...
I don't have anything against frontend, backend, full stack or programming itself. I enjoy programming and solving problems. I probably should've said server-side and client-side to make it more credible.
My main point is, companies (or clients) uses these terms to fool all parties. They are treating the developers as slaves and tricking however they can. That's all.
In fact this is really a good analysis, and I've never looked at it this way. I just saw "full stack" as a trendy, over-hyped, over-used and rather annoying "cliche" term which is nowadays being tacked onto everything ... everybody and their brother is calling themselves a "full stack dev".
I never realized that it's being used by companies or employers to take advantage of employees, but I get your point.
(in the same vein, I also notice the annoying over-use of the term "lightweight" that's being slapped onto every new framework or tool, no matter how light or heavy it really is ...)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Exactly! Just what I was thinking ... couldn't have said it better.
Also, if you're a freelancer/contractor (not an employee), it can be very beneficial if you can work in both areas (frontend and backend) - you can take on complete projects where both a frontend and a backend need to be built.
Finally, the article starts with:
"You specialize in PHP, ... none of which are related to frontend"
What's funny here is, of course, that PHP started out as a language to build frontends - just cranking out HTML. Nowadays separating frontend and backend is in vogue (using SPAs and APIs) but it's not always the case that the backend and the frontend duties are so clearly separated.
One thing I'll grant the author though, the term "full stack dev" is overused, you're seeing it way too often. By the way, is this article irony maybe? i noticed just now that the author is labeling himself as "full stack developer" ...
@mudasobwa and @leob , Absolutely valid points.
I don't have anything against frontend, backend, full stack or programming itself. I enjoy programming and solving problems. I probably should've said server-side and client-side to make it more credible.
My main point is, companies (or clients) uses these terms to fool all parties. They are treating the developers as slaves and tricking however they can. That's all.
Yes, I understand and appreciate your points!
In fact this is really a good analysis, and I've never looked at it this way. I just saw "full stack" as a trendy, over-hyped, over-used and rather annoying "cliche" term which is nowadays being tacked onto everything ... everybody and their brother is calling themselves a "full stack dev".
I never realized that it's being used by companies or employers to take advantage of employees, but I get your point.
(in the same vein, I also notice the annoying over-use of the term "lightweight" that's being slapped onto every new framework or tool, no matter how light or heavy it really is ...)