Hacker News new | past | comments | ask | show | jobs | submit login

I did this once on a personal project I was experimenting with. Then I started working on a change that turned out to be a lot bigger than I thought it was, and it ended up breaking everything. Trying to get it back to where it even worked again turned out to be so much effort that it totally killed any momentum I had.

So now I do everything in version control. Even minor little things I'm just playing around with. And I still use Dropbox as an extra failsafe against something happening to my version control repository.




>Once you actually need version control (as opposed to glorified backup) then you can switch for little to no cost.

>Then I started working on a change

I would say here that once you are working on changes, you need version control.


But what is programming if not changes? :) You start with a skeleton (be it a bare bones Sinatra server, or a .c file with only main() and a couple of functions), commit it, then change it.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: