43 Folders

Back to Work



”What’s 43 Folders?”

Vox Populi: Best practices for file naming






Ben shares how Pixel Corps does it, video style:











Dang. Thanks for that, Ben!

To repeat:


pm215's picture

I have to agree with...

I have to agree with Avi here about using some sort of version control system (as I'm sure did most of the other programmers reading this...). This is so much better than trying to stuff some sort of version information into the filename. And it's ten times as important as soon as there's more people than just you working on whatever it is. (I'm afraid the system airship describes for group working horrified me. Eventually somebody is going to screw up, delete files they shouldn't have done or upload an accidentally out-of-date file, and you're stuffed (assuming you even noticed...))

The only downside is that the traditional version control systems are rather optimised for the sorts of files programmers care about (plain text of various kinds) and although they will hold binary junk you can't do the useful "what changed between these two versions?" or "who put this line in this file?" operations. But even then you get the audit trail of "who changed this? when? what did they think they were doing?", you can back stuff out and the system prevents two people accidentally messing up each others' changes.




An Oblique Strategy:
Honor thy error as a hidden intention


Subscribe with Google Reader

Subscribe on Netvibes

Add to Technorati Favorites

Subscribe on Pageflakes

Add RSS feed

The Podcast Feed


Merlin used to crank. He’s not cranking any more.


Scared Shitless

Merlin’s scared. You’re scared. Everybody is scared.
