I concur with many of the others, directories are still a good way to organize your files:)
I have a three terabyte raid-5 Ubuntu file server I use to serve up the media in my house. I stick with a simple directory structure trying to keep it as shallow as possible:
This seems to work well for me, but just keep moving stuff around and you'll figure it out. File management is easy with Samba or your favorite SFTP client. I've also found that a bluray burner is good for stuff I want to keep, but in reality am never going to look at again.
Start by reading the developer documentation for the unit testing framework you are going to be using (junit for java, cppunit for c++, etc.)
Once you've mastered the basics of getting the framework installed and a basic test passing (e.g. assertTrue(true); ) check out xUnit test patterns. This book covers a lot of basic unit testing topics along with a number of things not to do while unit testing.
Slashdot Mirror
I wish they would've taken this approach with the Hudson CI server rather than fragmenting the community.
http://jenkins-ci.org/content/about-jenkins-ci
I concur with many of the others, directories are still a good way to organize your files :)
I have a three terabyte raid-5 Ubuntu file server I use to serve up the media in my house. I stick with a simple directory structure trying to keep it as shallow as possible:
This seems to work well for me, but just keep moving stuff around and you'll figure it out. File management is easy with Samba or your favorite SFTP client. I've also found that a bluray burner is good for stuff I want to keep, but in reality am never going to look at again.
Good Luck!
Start by reading the developer documentation for the unit testing framework you are going to be using (junit for java, cppunit for c++, etc.)
Once you've mastered the basics of getting the framework installed and a basic test passing (e.g. assertTrue(true); ) check out xUnit test patterns. This book covers a lot of basic unit testing topics along with a number of things not to do while unit testing.