@Tanner S. I do one Project per "Business Process?" I'm automating, one Repository per Project, then one Branch per modification (addition/bugfix/etc) I make to that Project

erictgrubaugh: Since I am internal dev and constantly making little changes as well as bigger project changes, I am thinking it may not be necessary to have a project per business process. I can just run my feature/fix branches

They identify what gets downloaded/uploaded and all your dependencies whenever you run `sdfcli deploy`; essentially if you have one monolithic project, every single time you deploy, you will redeploy every custom object in your account. I don't necessarily know of any issue with that, but your deploys will likely take a long time given how heavily customized your account is.

Do the custom objects drive anything like intellisense? Or could I just only keep the the custom objects that I am deploying at that time?

Not really anything to do with intellisense. An SDF Project is intended to be a collection of related custom objects/scripts/files that get deployed together. If you wanted to only deploy certain objects, I believe you'd have to drag things in and out of the

Objects

folder (or whatever your

deploy.xml

is pointing at) each time

ok cool, thank you. I think I will have to use it, and kinda get a clue on everything, then I will be able to make a more informed decision on how to use it. I appreciate you taking the time to respond!

Any time! I'm still getting used to it myself. As you probably remember, I like breaking things down into smaller everything. Smaller files, smaller functions, smaller modules, blah blah... 🙂

Hahah totally

Eclipse? I haven't used it for a long time, but last I did there was no code completion for 2.0. Still working on getting that working myself in WebStorm

it would be nice haha