What is the canonical approach to using a VCS right from a project's infancy?
Posted
by
Anonymous -
on Programmers
See other posts from Programmers
or by Anonymous -
Published on 2012-07-04T10:06:20Z
Indexed on
2012/07/04
15:23 UTC
Read the original article
Hit count: 196
Background
I've used VCS (mainly git
) in the past to manage many existing projects and it works great. Typically with an existing project, I would check in each change I make to the code that either optimizes or changes the overall functionality (you know what I mean, in suitable steps, not every single line I change).
Problem
One thing I've not had so much practise at is creating new projects. I'm in the process of starting a new project of my own that will probably grow quite large, but I'm finding that there is a lot to do and a lot changing in the first few days/hours/weeks/the period up until the product is actually functioning in it's most basic form.
Is there any point in me checking in each step of the process as I would with an existing project? I'm not breaking the project with changes I make since it isn't working yet. At the moment I've simply been using VCS as a backup at the end of each day, when I leave the computer.
My first few commits were things like "Basic directory structure in place" and "DB tables created". How should I use a VCS when starting a new project?
© Programmers or respective owner