4 ms·
This is a weird rant. He is complaining that someone who does many things won't be as good in front-end as someone who does only front end. ...ok? Nobody exp
by shp0ngle 8y ago
This is a weird rant.
He is complaining that someone who does many things won't be as good in front-end as someone who does only front end.
...ok?
Nobody expects full stack engineer to be all that great in front-end. That's why he is not a front end engineer.
Vice versa he won't probably be all that good in SQL or in administration and devops.
I am not even sure what is this guy complaining about exactly
- ricardobeat 8y agoDisagree. I expect full-stack developers to be _great_ at frontend, and _capable enough_ to build the backend. When resources are constrained you want the customer-facing side of the product to be a priority.
- Terr_ 8y ago> _great_ at frontend, and _capable enough_ to build the backend I think that bias says more about the particular kind of company you're in than the general label of "full-stack".
- gridspy 8y agoThat's a dangerous attitude. Both are important. Back-end is where the state of the application is. Where all the users are served, not just a single user. The back-end is where things are going to melt down with scale. If you make bad decisions in your backend you might find it hard not to lose customer data. They might also create user-visible latency or reliability issues. Front-end by contrast tends to keep working as well on day 100 as it did on day 1. If your point is that stable and boring back-end with shiny front-end is good, then yes, I agree with you.
- Glyptodon 8y agoSo you like putting lipstick on a pig.