Answer the question
In order to leave comments, you need to log in
How to program in a team?
Hello everyone)
Guys, just don’t laugh and don’t spit) I know how everyone loves newbies, I don’t like any amoebas myself) But pliz who has 5 minutes of time, share the information! So I decided to become a programmer, at first I studied for myself, then seriously, and now I did a test task, I was interviewed and they take me)))))) I go out right after the holidays! But I'm a little dumb, because I don't know how command programming works at all! Explain pliz on the fingers ... how it all happens!
Answer the question
In order to leave comments, you need to log in
You will be given a curator, he will give you specific tasks.
You should be given links to documentation or show how their work is organized.
You are actively trying to read all the documentation, buy a notebook, draw diagrams for the first month in order to better understand.
Pull the curator not every 5 seconds, but collect a few questions, come and find out.
A couple of times a week, check with him in terms of what is expected of you - what kind of performance, in order to understand you have time, overtake or lag behind expectations. That is, you just go out with him to the meeting room 1 on 1, and specify how and what tasks you get, what you don’t, what is expected that you will have time to do before the next meeting and before the end of the month.
It is not necessary to do everything in the first weeks, it is more important to figure out how to work correctly. You have three whole months to do this, and it will be possible to understand whether you are coping well only in a month or two.
The team must use the version control system - GIT, Mercurial - and task trackers - Jira, Redmine. You need to know. How to write code - look at other people's sources, ask your colleagues, for good there should be a style guide, but they are too lazy to do it - just ask the team leader to tell you how to.
Just like any other team work) The project is divided into sections, and each of the sections is entrusted to someone. Further, all you need to remember is to follow the development patterns adopted by the team, remember about the code style and carefully watch what happens in neighboring areas so as not to break something with your work.
Don't worry. You won't be programming anything for the next couple of years, you'll be running for beer and cigarettes. Most importantly, listen to your elders and carefully watch what and how others do.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question