Not entirely sure what you mean by "high quality of sas macro writting" so going to assume some sort of global library based tool approach. What I would suggest is to learn some of the principals of Software Development. Basically everything comes down to a process with inputs and outputs, so this can be documented (Functional Design Specification), where all the information on the process should be documented. Once you have this done, and the testing setup (and possibly user documentation), actually writing code is next to nothing in the whole scheme of things.
As for macro itself, quite a few people find that writing the code to do the process, then re-factoring that working code by replacing repeating parts, parameterising changing variables etc. helps.
One thing I would also add is to not hide anything, make your code as simple, easy to read, and open as you possibly can do. Sure, we ca all write funky routines, which call compiled procedures within masses of brackets and macro calls and references, but would you like to be the person who has to either use that or try to fix/update it in the future?
