Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

Re^2: just wanted to show what I managed to write with your help

by perltux (Monk)
on Nov 12, 2012 at 13:07 UTC ( #1003434=note: print w/replies, xml ) Need Help??

in reply to Re: just wanted to show what I managed to write with your help
in thread just wanted to show what I managed to write with your help

I might start using github or something like that once the code is a bit more mature. Right now I'm working so much on it still that the overhead of using a version control system would be a hindrance for me especially since I have no experience with them (other than some experience with cvs 10-15 years ago and I hated it! ;) ) so I would first have to learn how to use git.

That said if you are offering to collaborate on the code, then let me know, I'm sure we can work something out! :)
  • Comment on Re^2: just wanted to show what I managed to write with your help

Replies are listed 'Best First'.
Re^3: just wanted to show what I managed to write with your help
by choroba (Bishop) on Nov 12, 2012 at 13:09 UTC
    Believe me, the overhead of using a version control system is negligible compared to the overhead of not using it.
    لսႽ ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ
      I'm sure you are right, but the overhead of first learning how to use it is not negligible! :)

      Seriously I certainly see the point in using one once more than one person works on the code, but right now it's only me.

      Again if anyone wants to collaborate, just let me know and I'll start learning how to use git and github.

        I would second choroba's suggestion to use a revision control system of some sort (git, svn). It allows you to 'erase' mistakes or back track to a point where your code was working. It is also nice to be able to take multiple divergent paths when testing out if something will work, and to be able to select the parts that work best.


        As well as code colaboration, a project Wiki and issue tracking git is also very handy for people wanting to download your works:

        git clone

        FWIW, learning git isn't too critical, as long as you archive your directory before adding new features and bump the version (hey, its The Git Parable (how git works, inventing git ))

        you can turn zip-files into a git repo when/if there is a demand ( if gitpan can do it :)

        But if you do want to learn it I recommend (Git HowTo TOC in spoiler)

        • 1. Preparation
        • 2. The final preparation
        • 3. Creating a Project
        • 4. Checking the status of the repository
        • 5. Making changes
        • 6. Staging the changes
        • 7. Staging and committing
        • 8. Commiting the changes
        • 9. Changes, not files
        • 10. History
        • 11. Aliases
        • 12. Getting older versions
        • 13. Tagging versions
        • 14. Discarding local changes (before staging)
        • 15. Cancel Staged changes (before committing)
        • 16. Cancelling commits
        • 17. Removing a commit from a branch
        • 18. Removing the oops tag
        • 19. Changing commits
        • 20. Moving files
        • 21. More information about the structure
        • 22. Inside Git: .Git directory
        • 23. Git inside: Direct work with git objects
        • 24. Creating a Branch
        • 25. Navigating Branches
        • 26. Changes to master branch
        • 27. View the different branches
        • 28. Merging
        • 29. Creating a conflict
        • 30. Resolving Conflicts
        • 31. Relocating as an alternative to merging
        • 32. Resetting the style branch
        • 33. Reset of the Master branch
        • 34. Rebase
        • 35. Merging to the Master branch
        • 36. Multiple repositories
        • 37. Cloning repositories
        • 38. Examine the cloned repository
        • 39. What is origin?
        • 40. Remote branches
        • 41. Changing the original repository
        • 42. Fetching changes
        • 43. Merging pulled changes
        • 44. Pulling and merging changes
        • 45. Adding a tracking branch
        • 46. Bare repos
        • 47. Adding a remote repository
        • 48. Submitting changes
        • 49. Removing common changes
        • 50. Placing your git repository
        • 51. Sharing repositories
        • Thank you!
Re^3: just wanted to show what I managed to write with your help
by GrandFather (Sage) on Nov 12, 2012 at 19:47 UTC

    Your thinking is exactly backwards! Revision control systems are to help you and to save you arse when you do something dumb (and believe me, we all do dumb things). At the very least set up a git (or Mercurial) repository for each project you are working on right now. You don't need to share the repo now, or ever, but you get no benefit at all from it at the end of the project!

    You may find Mercurial easier to get your head around than git, especially if you can use TortoiseHg (Wikipedia article). Modern systems like git and Mercurial take a snapshot of the current state of your project and deal with your entire project as an entity. CVS was a file at a time system and made a lot of stuff hard to do and difficult to understand.

    True laziness is hard work
Re^3: just wanted to show what I managed to write with your help
by petdance (Parson) on Nov 12, 2012 at 17:22 UTC
    How much overhead is it if you accidentally delete working code? Or if you change previously-working code and then you don't discover it for days and now you can't go back and figure out what your change was that broke it, and for that matter, you don't even know what your last working code looked like?


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1003434]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others browsing the Monastery: (2)
As of 2018-04-20 05:23 GMT
Find Nodes?
    Voting Booth?