I've had this conversation a lot over the years about folks complaining about the documentation (or supposed lack of it). The PB manual is identical in format to the PBP manual and yes, there's that flashing LED program there to get you started. Each command is explained in the manuals, and more often than not there is also an example of usage shown. The MeLabs site has lots of sample programs so that there is also familiarity of the structure of a PIC program.

What people purchase is a COMPILER (which does it's job very well) and not a complete educational course in Basic. Where should a software author stop documenting? One has to make an assumption somewhere down the line that the user knows how to program in Basic.

If you buy an accounts package, you don't get an accounting course thrown in for free. If you buy a CAD package, it doesn't come with an integral course in archetectural design. If you buy a book, the author has assumed (and it is generally accepted) that you have learnt to read. Likewise with a Compiler.

Unfortunately, I've discovered that lots of people with PB (and PBP) are totally clueless. They rely on Cut and Paste from other peoples code without having the vaugest idea of what they're doing. If there was a book showing you how to build and program a Weather Station, somebody would complain that the example had SEROUT for comms instead of HSEROUT, and that it was written for a 16F628 and not a 16F628A. You just can't win.

The best book IS the MeLabs manual supplimented by the PIC's Datasheet. There's also no substitute for experience - and you don't get that from books... you get that from sitting and doing and learning from your mistakes... you get that from writing code, and analysing line by line, instruction by instruction what's happening.