Gregory's Server@mrcompletely @mhoye
My BEng course included plenty of "working in teams" exercises, but didn't do a good job of teaching team work or having retrospectives on how the teams worked.
|
Top-level
7 comments
@JMMaok @mrcompletely @mhoye  @spodlife @mhoye curious if they were cross disciplinary teams or just a group of coders with similar skill sets? To me, a generic fully staffed dev team includes full stack engrs, front end specialist devs, possibly back end specialist devs, UX, PM, QA, plus product ownership and business stakeholders, with their actions mediated by a ticket system, chats, etc. Coding with other coders is the least of it. And then there's all the variations in team size/composition/style I mentioned elsewhere @spodlife @mhoye if the functional spec isn't clear do you know who to ask? If one of your issues bounces off QA after your code review and merge, do you pick it up or does it go back on the pile? If you pick it up, how do you know whether to do that or your current ticket first? What if you get 3 unfair seeming code review thumbs down in a row from the same person? How do you handle that? What if someone you like is heavily slacking or writing bad code? These are all things I've seen this week @spodlife @mhoye no, the unfair seeming reviews were last week 😂 Edit: note I'm not asking schools to teach answers to these questions since every shop has its own style. Just to make people aware of these dimensions to the work, which by and large seem to be totally opaque to recent grads unless they had a great internship experience. Also note I do generally like hiring recent CS grads overall when they fit our needs so I'm not just bitching about The Youths here @mrcompletely @mhoye |
@spodlife @mrcompletely @mhoye
Yes, this is very true and important. A lot of faculty avoid teamwork themselves. A good research-based tool to improve student teamwork is CATME.org.