1–10 of 41 posts
The front end landscape has always seemed quite messy and fragmented to me, and honestly a bit scary too. I am fine with taking the leap of faith, but wanted HN community's opinion on whether it would be an enlightening experience. Is there something like "too late to move to front end"?
Front-end is fast moving indeed. I don't have any definitive answers for you, other than to say that in the front-end vs. back-end equation, front-end is lot less stable and is going to require more time keeping up with new developments.
Whenever I've assigned web work to developers I assign in terms of functionality and they write front and back. I think this is quicker than trying to communicate between two teams.
But to answer the question, why not. Then you're a full stack developer.
I've never understood the split between front end and back end. Whenever I've assigned web work to developers I assign in terms of functionality and they write front and back. I think this is quicker than trying to communicate between two teams. But to answer the question, why not. Then you're a full stack developer.
Sure, for simple enough projects a single person can do both, but doing that severely limits your potential scope.
For more complex projects, it's more convenient to have someone who specializes in carpentry provide the specs for what the welder needs to provide.
I've never understood the split between front end and back end. Whenever I've assigned web work to developers I assign in terms of functionality and they write front and back. I think this is quicker than trying to communicate between two teams. But to answer the question, why not. Then you're a full stack developer.
If you can handle the fragmentation of unix environments, you can handle the fragmentation of frontend frameworks. You probably won't find any enlightenment though, unless you dive into gpu programming or such.
The upside is that they're much more transferable between companies. Everyone wants to hire experts in their current back end stack, but everyone needs CSS & JS.
I've never understood the split between front end and back end. Whenever I've assigned web work to developers I assign in terms of functionality and they write front and back. I think this is quicker than trying to communicate between two teams. But to answer the question, why not. Then you're a full stack developer.
This is like saying you never understood the split between a carpenter and a welder, when both are involved in producing the finished product of say, a cabinet. Sure, for simple enough projects a single person can do both, but doing that severely limits your potential scope. For more complex projects, it's more convenient to have someone who specializes in carpentry provide the specs for what the welder needs to prov…
The reason the fe/be distinction exists is mostly management, accounting, and legacy, not the actual work. These days the engineering itself can be interchangeable across the "ends", depending on the toolset you're using.