3 ms·
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
by 1ba9115454 9y ago
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.
- Sorreah 9y agoThis 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 provide.
- virsimil 9y agoNo, because a carpenter can't switch out for a welding torch with a hotkey. Nor can they woodwork with the torch. 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.
- NikolaeVarius 9y agoDifference between knowing it and being good at it. Knowing how to do a join query does not make you a full stack dev