Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
You have a team. It's up to you to manage them. If said friend isn't great at coding but comes up with ideas, give them something that works well with their style of working. Prototyping, ideation, tracking down logic errors, etc. Everyone has different skillets and expecting people to conform in such a short time is impractical. It works in say a job because you have time to introduce people to a common process, but in a scenario like this I'd go for specialization.
That or you have a serious talk with them about what you expect, and ask them to leave if you can't agree on it. -
@RememberMe Finally we established a workflow, so that everyone is happy and can contribute, but it wasn't easy gosh
Related Rants
We all have our favourites
True!
This year I and two friends joined modelling competition for uni students called SCUDEM. We are modelling refugee settlements and the crime rate in Uganda. I try to lead the group as the previous year and we changed one team member. The model is written in Julia and it is 2k of working lines after week, we work on it in our spare time.
However, one friend who hasn’t done any bigger project in the past or wasn’t programming for money disagree with the workflow. He prefers doing some small models separately. He doesn’t write clear code and it is difficult to read it afterwards. His ideas are good, but he likes more to talk about the problems than straight code them down in the way that we can use it in the bigger structure.
Do you any ideas on how to motivate him to take part in the collective workflow? I feel that working separately is rather contra-productive.
question
workflow
julia