All geek questions in one place

Anyone have any tips on organizing / managing solo development efforts?

I have a project with which I am starting to work, this is a solo project, but I would like to try to stay organized and have some methodology for work. Most of the methodologies I've seen focus on teams. I am wondering if anyone has any links or thoughts on planning / creating a project using the system as a solo developer. Thanks in advance, John

+3
source share
9 answers

Set up the source code repository (I use perforce) and check back often for changes. It is tempting not to do this when you are working alone, but even when you are not bothered by the competition for the source files, having a record of where you were can be valuable.

The task of getting to the checkpoint every day will also help you create micro goals, which in turn will help you think about how you break the problem down to bite-sized pieces.

+8
source

- . , TDD, . , , , . , ( ), . , .

, - , . , , . , , .

, , XP, : -)

+3

Moleskin Microsoft excel.

moleskin, , . .

microsoft excel, . , TODO, ( " , ", " " ) .

. .

robocopy MS . ( Subversion), .

. , - .

+2

, .

  • , .
  • .
  • , - .
  • , , , - , .

, , . .

+1

, , . , ; , . Ruby/Rails, : . Ruby

, , - , , , , . , , . , , , , , .

, . , , .

+1

. . , , . 10 , 18 . 3/4 , , 18 . 10 . .

0

,

, ,

/ , , ,

0

- , Basecamp ( , , , - , ). . (php, html ..), Eclipse CVS.

. , .

0

It’s good for me to follow TDD (Test Driven Development) and always end a development session with a few failed tests. When I return to the project (which can only be in a couple of days), I have a logical starting point. This helps me get into the groove faster and not look at my IDE for 2 hours.

0
source

Source: https://habr.com/ru/post/1726563/

More articles:


All Articles