+1 on that Bob.

It's always best to start small. You may eventually get it right but you're much more likely to get it right if you start small and learn what works and what doesn't.

And even if you did get it right, would you know why? I used to be a programmer and would preach the benefits of changing code one snippet at a time only, then testing, then changing something else, then testing. My bosses used to get on my case about the waste of time. But if you change more than one thing at a time, you don't know what change fixed or broke your code.

Jumping to the final product can be the same way with cooking. You learn a lot of valuable lessons when you start small and build your way up. I like to think I'm half decent in the kitchen but I wouldn't be half as good if I hadn't experimented with stuff, made some mistakes, and learned lessons about what works and what doesn't.

To me it's like giving somebody who's never seen a microwave before a microwave and a turkey and asking them to make a perfect Thanksgiving feast. There's no way they'd know how to do it or know if it were even possible. And even if they got it right, they'd go through a lot of Turkeys learning stuff we take for granted because we've used microwaves on little stuff for years and take it for granted.