Hacker News Reader

Comment by ing33k | Hacker News Reader

"Engineers should teach engineers GIT, designers should teach designers GIT."

is git part of modern design workflow ? how are designers using git ?

At any scale, git is probably not going to be your best bet. svn might actually be a better option as it allows you to checkout just the parts of the repository that you need.

More crucially, it doesn't keep the entire history locally (just working copy and a the latest(ish) version in the repository). This really starts to matter when you have 200mb PSDs.

There are probably even better options out there (though previous searches didn't reveal anything I particularly got on with) - there are certainly better options than git.

Ideally something based around the dropbox model (doing block level deduplication) would be wonderful. Maybe such a product exists?

git does allow you to check out only a selection of version history

Oh ok, but that's not how it would operate, right? So, say it was just me working on a project using a psd. If I committed it a couple of times a day, I'd end up with all the old copies in the local object store. Maybe it's possible to clear those out, somehow? Either way, you'll find that you have to jump through hoops to get reasonable behaviour with git in this use case.

I see I've been downvoted for my previous comment. I'd appreciate a justification from the downvoter as this is actually an area in which I have some experience.

All sorts of assets have been stored in version control systems for decades now. That includes designs, images, documents, specifications, and so forth.

I was talking about the 10% of the time designers should be coding in this type of environment. (I.e. pushing polish code or hacking together a quick marketing page.)

Clone the repository and start a webapp locally to tweak CSS and do other designery things.

Reply on news.ycombinator.com