To me it's all about the impact you can make over a period of time, while at the same time enjoying your work (which means spending 80% of your time reading code and not going bunkers).
I find Frontend applications to be short-lived in comparison with Backend ones. Many new websites work with Backend cores that are decades old.
I also find Frontend code to be much more messy and hacky. I don't know why, I guess JS has a double edge between expressiveness and just pure anarchy.
In general, when working with a medium-sized or larger team I dislike doing Front-end work. I really get the feeling of having too many cooks on the kitchen very quick. Yes, everybody codes the backend in a different way, but at least not in an altogether different paradigm!
However, I also like the 'indie' feeling of Frontend development and how easy and cheap is to prototype user-ready applications.
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.
To me it's all about the impact you can make over a period of time, while at the same time enjoying your work (which means spending 80% of your time reading code and not going bunkers).
I find Frontend applications to be short-lived in comparison with Backend ones. Many new websites work with Backend cores that are decades old.
I also find Frontend code to be much more messy and hacky. I don't know why, I guess JS has a double edge between expressiveness and just pure anarchy.
In general, when working with a medium-sized or larger team I dislike doing Front-end work. I really get the feeling of having too many cooks on the kitchen very quick. Yes, everybody codes the backend in a different way, but at least not in an altogether different paradigm!
However, I also like the 'indie' feeling of Frontend development and how easy and cheap is to prototype user-ready applications.