@adamhsparks Is there a *GOOD* introduction to {targets} that actually makes it immediately appealing? I've tried a few times to pick it up and feel like I'm taking on a new language, adding a lot of learning time I struggle not to feel is wasted.

I've been told my approach to project workflows is very similar to the way {targets} works, just replacing their much better systems with a ton of loops, if statements, and checking of filesizes/dates etc.

I need to pick it up, but that initial approach was tough to get over.

@tootstorm @adamhsparks I put a lot of effort converting a project to {targets} just in order to learn it - it was painful, it took forever, it was very confusing, and I'm not sure if I really did it the most efficient way.

But then, 4 months later, I was asked to run the analysis again with some slightly different data. It took like 15 seconds, it was amazing.

@jimbob @tootstorm @adamhsparks Everything we do now is a {targets} pipeline. My approach is thinking through where I might want discrete datasets to have available for future action. I then make functions that get me from my raw inputs to the next step.