4 ms·
At my last startup, we tried full stack development in conjunction with pair programming. Fullstack dev is hard essentially have to be great at both back and fr
by karmakaze 8y ago
At my last startup, we tried full stack development in conjunction with pair programming. Fullstack dev is hard essentially have to be great at both back and front end and some UX. Pairing helped. In the end many didn't want to continue preferring to specialize. That was a shame because like pairing, full stack is a nonstop dev flow, no pauses for talking to other 'end' nor code review delay.
Because it's hard to build that culture it's ew rely done and so there's no market for it. What full stack means in the market is front end with a little back end and doesn't pay specialty rates. Actual full stack is a specialty just so rare it's not even 'a thing' in the minds of employers.
- nickstefan12 8y ago> What full stack means in the market is front end with a little back end So much this. I believe in full stack development skills, that someone can have them, but I don’t believe in the job role of full stack developer. At small medium scale, there’s just so much more front end work on a lot of apps. Let’s say 70%. My experience with full stack as a job role is that it turns into “what backend change can I quickly make in order to get back to the front end work which is most of the work.” Which then means no ones manning the ship / design / scope creep / perf risks etc of the backend. I think separate roles lead to more even evaluation of best feature implementations.