I’m novice developer, working alone. I’m using Xcode and git version control. Probably I’m not properly organised and doing things wrong, but I’m usually deciding to do commit just to make safe point before I’m spoiling everything. And at that moment I find it difficult to properly describe what I have already done, but I know exactly what I’m going to try next. So when I will do next reference point the previous is already named.
So my question is – are there some version control methodology where reference points are described by plans, not facts. Why this could be a bad idea?
ABC, always be committing. While you may be working on projects for yourself an no one is accountable but yourself, it is generally a good idea to commit what has been done rather than what you plan to do.
Branching is designed to save yourself from what you plan to do. Create a branch called ‘addnewscreen’ or whatever you plan to do. This way you can keep committing all the small changes on your new stuff without polluting your main branch. Once you are happy, merge it back in and make a new branch for what’s next.
If you get stuck, the Pro-Git Book has helped me so many times I’ve lost count. Hopefully this will help you too. Good luck.