Speaker & Tech Explorer DevOps @Omniplan. Developing in mainly in Angular and WebAPI. Loves learning, reading, music, cars and my family (not in that order!). MVP Developer Technologies
We've just got a new (to our team) front ender and the way that we have resolved it is to make sure that we pair with him - both FE and BE. That way he gets a better understanding of the work, and so do we.
And this spills over into the refining - we all work on it all so we all need to take part. Sure he doesn't know the language yet, but he's starting to know the complexities, and we have the same when looking into the FE parts of our stories.
It's not a fast process, but we do see benefits already.
Speaker & Tech Explorer DevOps @Omniplan. Developing in mainly in Angular and WebAPI. Loves learning, reading, music, cars and my family (not in that order!). MVP Developer Technologies
Yes, we try to pair as much as possible, and our recent change has been to include our FE team member in these sessions, rather than splitting the work and finishing it separately.
Speaker & Tech Explorer DevOps @Omniplan. Developing in mainly in Angular and WebAPI. Loves learning, reading, music, cars and my family (not in that order!). MVP Developer Technologies
Speaker & Tech Explorer DevOps @Omniplan. Developing in mainly in Angular and WebAPI. Loves learning, reading, music, cars and my family (not in that order!). MVP Developer Technologies
I think that to begin with we want a deeper understanding, and gain some extra skills (rather than asking the FE or BE to do tasks that we should really be able to do).
Where it goes long term? I have no idea - but I'm looking forward to the journey!
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.
This is a problem we have as well.
We've just got a new (to our team) front ender and the way that we have resolved it is to make sure that we pair with him - both FE and BE. That way he gets a better understanding of the work, and so do we.
And this spills over into the refining - we all work on it all so we all need to take part. Sure he doesn't know the language yet, but he's starting to know the complexities, and we have the same when looking into the FE parts of our stories.
It's not a fast process, but we do see benefits already.
Thanks for sharing! Pairing - you mean pair-programming sessions?
Yes, we try to pair as much as possible, and our recent change has been to include our FE team member in these sessions, rather than splitting the work and finishing it separately.
Does it mean that BE dev and FE dev together first finish some BE task and yhen together do some FE task?
Yes, that's it. As a team we pick up a story, and try to make sure our stories as complete functionality - and not split across technical lines.
We split the work for that story into tasks in a way that allows us all to work on it.
And then we pair to get it completed.
We're still learning, but now we've got some experience we really see the benefits of working this way!
Sounds interesting! Do you plan devs to become fullstack finally, or your goal is just to get deeper understanding accross FE and BE?
I think that to begin with we want a deeper understanding, and gain some extra skills (rather than asking the FE or BE to do tasks that we should really be able to do).
Where it goes long term? I have no idea - but I'm looking forward to the journey!