Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×

Comment Re:depends on the scope of the project (Score 3, Insightful) 72

No no no no no. :)

Whether you're working in a team or working by yourself: Use Subversion Anyway. Or svk. Or Darcs. Any reputable revision control system will kick the pants out of any ad-hoc solution you come up with. Revision control should be automatic and easy. The value of being able to easily merge changesets alone is reason enough for any non-trivial project. Keeping track of branches for experimental/delicate changes, tagging releases, LOG MESSAGES for all your changes - all of these things, use them, learn to love them. It's a bitch to get in the habit, but when you do it's absolutely worth it.

It's taken me over seven years to truly learn the worth of version control. These days I'd dare not live without it. It really is that good. Honest!

User Journal

Journal Journal: RAILS!

Oh. My. God.

Ruby on Rails.

I just started playing around with it tonight ... it took me around ten minutes with little prior Ruby experience and NO prior Rails experince to do what took me around two hours in PHP (a language I've been using for about six years, four years commercially).

Wow.

Admittedly at the moment it's just a toy application. But at the very least, Ruby on Rails has earned it's place in my heart as a rapid prototyping tool.

User Journal

Journal Journal: XUL/XPCOM+PHP vs. Applets+PHP

Hmm ... maybe it's time I started writing in this Slashdot journal thing of mine. I mean, god, it's only been three years or so since I've registered with Slashdot.

Slashdot Top Deals

The hardest part of climbing the ladder of success is getting through the crowd at the bottom.

Working...