How to do code version analysis in order to control a remote developer?

B

blabs2015-10-19 13:24:54

PHP

blabs, 2015-10-19 13:24:54

I plan to organize work with developers remotely, for this I need to understand how much work the programmer performs in a certain period of time. We track his work through trello, but we want to understand what is really happening with the code.
Tell me a tool that will allow us to
1. compare code versions before and after (for example, a day)
2. understand how much code has been added (specifically what code)
3. what files have been changed
4. work logs
Work is being done on the server.

Reply

Answer the question

In order to leave comments, you need to log in

5 answer(s)

A

Alexey Skobkin, 2015-10-19
@skobkin

Git ( wiki ).

S

Saboteur, 2015-10-19
@saboteur_kiev

Any version control system. Git is one of the most popular right now. The developer posts all his changes to the system, as a result, you can track all changes by date or by "commits".
Between different commits, you can analyze both the standard line counts (number of changed / added / deleted lines), and a specific view of changes.
But in principle, if you are satisfied with the work in terms of "a task is given, a solution is received", then the number of lines is an indicator of nothing at all, and viewing changes directly in the code is better to be carried out by a competent specialist who could evaluate the quality.

A

Andrew, 2015-10-19
@R0dger

1. git
2. git
3. git
4 - unlikely to be...
as an option there is wakatime.com, there is support for popular editors .. and let him give you a link.

N

Nikolai Markov, 2015-10-20
@manameiz

Judging the work done by the code is a very bad idea. You need to look at the final result, at "what" was done and what quality.

D

Dmitry Alekseev, 2015-10-19
@dalexeyev

> Prompt tool
Version control system. git, mercurial, svn. It's in that order.
> 1. compare code versions before and after (for example, a day)
Graphical client (for example, tortoise) will show in color a list of changes by code by commits
Commits are tied to time
> 2. understand how much code was added (specifically what code)
Graphical client everything will be clearly shown
> 3. which files have been changed
Including the list of files
> 4. work logs
each commit is accompanied by a comment, so you will have a list of "developer comment" - "diff file"