And remember: there is nothing worrying about getting stuck for days and not seeing what is wrong, especially when you are learning! In the end, it is that one split second of understanding why it doesn't work which leads to true understanding, not 10.000 dodgy examples from the internet (and I'm not referring to Michael...). So if you get stuck in the future: don't panic, it's normal. Of course, this used to be more common 15 years ago, now you can have dozens of internet buddies to help you out. But getting stuck and finding your own way out is actually a good experience.

btw, Patrick, I think that with 'db' he means not database, but the db directive, and then use movc @a+dptr to read the data.
Is this a good idea? Well, I wouldn't say that it is or isn't, but rather that it is more important to have a good strategy planned towards what you want to do. Which precise instructions you then use to implement that strategy is of minor importance. I would even claim that if you have a good idea about strategy (how to approach a certain problem) it doesn't matter at all on which processor you are asked to program on. You will be able to find your way around on any.

I would stay away from writing tutorials until you really, really, actually know what you are doing which may take years of experience. There is enough dodgy material on the internet as it is already. There is no shame in NOT writing half-assed stuff.