4 ms·
Early on you don't know the distribution of work. If it turns out that your workload doesn't split 50/50 front end/back end then half your team will be overwor
by dagw 9y ago
Early on you don't know the distribution of work. If it turns out that your workload doesn't split 50/50 front end/back end then half your team will be overworked and half your team will be waiting for stuff to do. Once you get going it might turn out that the back end wasn't that hard after all and that your true USP is your world class front end (or vice versa).
Once things settle down into familiar pattern and you actually have a good idea of what your workload will look like down the road and what specialists you actually need (as oppose to imagine that you might need), then you can start hiring specialists.
Edit: That being said you should have someone responsible for each part and you can split your team into primary front-end and primary back-end based on their relative strength and preferences. However it's important that everybody has the necessary skills to work on all parts of the product in the beginning.
- marpstar 9y agoThis, and the fact that most companies don't have the luxury of having the choice. Sure, maybe in the Valley you can find expert front-end and back-end devs just around the corner, but in the Midwest USA, you take whatever competent developers you can get. Most people I know have never really worked in the sort of "specialist" position OP talks about, so most of the time they've already got "full stack" (okay, maybe not FULL stack, but...) experience, so we just run with it. I work 9-5 for a company where 90% of the devs are "full stack". Rarely are the people who "specialize" actually any sort of expert, instead their skill-level on their weaker side of the stack is just especially low.
- tedmiston 9y agoInteresting how perspectives differs. I work for a startup where all devs are specialized (headcount is ~50). At startups in the midwest I've worked almost exclusively with specialist devs. Occasionally in the early days a back end dev might also do front end work but in my experience that's far less common with scale. While we might not be able to find a senior back end dev with production experience in our preferred language / framework easily locally, we can definitely find back end vs front end at various levels of experience. AngelList is helpful for this. Front end used to be something you could just do on the side on a whim as a backend dev but as the front end web frameworks have emerged and evolved, and consequently more work has moved to the front end this has changed in the past five years or so.
- nitwit005 9y agoYou can generalize this to a "weakest link" issue. If you imagine splitting things into 100 expert teams instead of just 2, it becomes pretty clear that things will move as fast as the slowest team (assuming a linear chain of dependencies). Unfortunately hit such situations quite a bit at my current workplace...