Easy way to store source code?

[Krice]

Is there such thing? I don't want anything like source control (too difficult and hacky), just store and possibly share source code (maybe with new version of Teemu).

[tuturto]

Google drive, drop box, wuala, ubuntu one.. There are number of solutions designed to just store and share arbitary documents. You miss most advantages of source control, but set up and usage is easy.

[kraflab]

I use dropbox.  You can choose to "share" a folder with other people you want involved and the files sync automatically.

[Z]

Using version control (I think that's what you mean by source control) is worth it. I find git hard to grasp, but Subversion is fine.

[TheCreator]

Try TortoiseSVN, it's very easy. The power of version control can't be overestimated. Whenever something in your code breaks, you can review the changes and find the bug. Without version control all you can do is guessing.

[Krice]

Whenever something in your code breaks, you can review the changes and find the bug.

I don't have bugs. At least bugs I don't know. The idea of finding bugs by tracking changes sounds primitive. I'll try Google Drive, I have an account for Google anyway.

[TheCreator]

I don't have bugs. At least bugs I don't know.

So you don't know that you have bugs. One day you will learn of their presence (most likely when someone else will attempt to run your code) and you will regret not having version control. Finding bugs by tracking changes may indeed sound primitive, because it *is* primitive (although I'd choose a better word: easy). The best thing about this method is that you have the complete information about what could have caused your program to fail, so that if your program crashes at random places because of memory corruption, you know where to start looking for a bug.

[kraflab]

I don't have bugs. At least bugs I don't know.

So you don't know that you have bugs. One day you will learn of their presence (most likely when someone else will attempt to run your code) and you will regret not having version control. Finding bugs by tracking changes may indeed sound primitive, because it *is* primitive (although I'd choose a better word: easy). The best thing about this method is that you have the complete information about what could have caused your program to fail, so that if your program crashes at random places because of memory corruption, you know where to start looking for a bug.

I, like Krice, am a real developer, and our versions play with permadeath on!

[Krice]

so that if your program crashes at random places because of memory corruption, you know where to start looking for a bug.

In case of C/C++ you don't know. It can be anywhere. Version control doesn't help you unless the bug actually was programmed recently which is just one possibility. But I really don't need version control, because my source code is quite bug free. These days I don't even need to use a debugger. I've learned to take care of the weak points of C++ which usually produce bugs.

[MorleyDev]

I recommend version control. You pick up the basics of git pretty quickly, and it's another tool in your belt.

Plus it allows you to safely experiment and spike out new ideas with a safe roll-back point. Then when the ideas are more fleshed out you can roll back and integrate the features properly.

Most of my code tends to be bug free due to being very loosely coupled with heavy test coverage (so I get near instant feedback if things are not as expected, and can track down issues quickly), though things will still occasionally slip past.

Plus, I like the peace of mind of knowing if things blow up I have a relatively painless way to roll back.

Also issue trackers are a good way to map out features to be implemented, though admittedly not intended for this and github's issue tracker is no JIRA...

[AgingMinotaur]

zip

As always,
Minotauros

[TheCreator]

In case of C/C++ you don't know. It can be anywhere. Version control doesn't help you unless the bug actually was programmed recently which is just one possibility.

Even if this happens, having version history is still much better than nothing. You have, say, 80% certainty that the bug is in the last revision, 40% that it has been made in the revision before the last one, and so on. Without version control you have 100% certainty that the bug is in your code and that's all you know . However, memory errors are not so very common if you're an experienced C++ programmer and the real reason why you should use version control is that it remembers all the small changes that you don't. How many times did it happen to you that you realized a feature had been working in the past, but now it's broken? What do you do in such cases? Look at file modification dates to see what has been changed quite recently? Try to guess? Modify a randomly chosen file, hoping that it will fix the problem?

[Krice]

How many times did it happen to you that you realized a feature had been working in the past, but now it's broken?

How about zero times. If I say I don't need version control it means I don't need it.

[TheCreator]

How about zero times. If I say I don't need version control it means I don't need it.

No, it means that you don't realize you need it (yet). Or maybe you're working on some 7drl that has roughly 2k lines of code.

[Krice]

Or maybe you're working on some 7drl that has roughly 2k lines of code.

Kaduria has 44K and Teemu 19K.