In most cases, this is false. Like any programming language, it takes time to learn the intricacies of it. Believing that you can learn any programming language (without prior or similar experience in another language) is akin to thinking that you will be able to learn Spanish in a week. The reality is that by the time you have finished your first document assembly system, you will wish to start it over, as you have learned so much since commencing the project. The learning curve for the first few months is almost straight up.

The easier something is to learn, the less functional it is likely to be. Why? Software that takes longer to learn takes longer because there is more to learn (generally). The less features and functions you have to wrap your head around, the less time it takes. This usually translates directly into less functions/tools/approaches to actually use later.

A more likely timeline is something like...

• Toss around idea of document assembly for a few months, look at products.
• Eventually purchase a document assembly product.
• Get two days training.
• Forget half of what you learned because it was crammed into your head inside 2 x 8 hour days.
• Start "programming"...refer to manual, look at help files, call support.
• Stumble, skin your knees, fall over some more. Post email to list-serve email group for help and get response day or so later.
• Finalize document #1.
• Rinse and repeat for as many documents are you are trying to program.
• "Finish" library #1, go back to start of library to check up on some things you couldn't do at the time, but can probably do now.
• Upon reading code, fight the urge to rebuild entire library from scratch.
• Start library #2 while still receiving feedback from library #1.  Make edits to library #1, still fighting the urge to rebuild the entire thing.  Rinse and repeat above points until library #2 is done.
• Library #3 starts to get better...

A slow process of learning. In almost every case of a budding document assembly developer, the learning curve is straight up for MONTHS. We have dealt with document assembly developers with YEARS of experience who are still only aware of half of what their product can do. How can this be so? Because if you've never been exposed to "heavy" or "complex" programming, most likely you are not going to be aware of how far you can take your product. It is impossible to learn advanced techniques if you've never been exposed to them...