I come from the developer rather than the DBA perspective and the article is still definitely applicable. I'd go one step further though. I don't just aim to be replacable, I aim not to need to be replaced. If I can leave a client with a product that no longer requires a programmer then, and only then, is my work truly done.

The greatest compliment I can be paid is to be made redundant by a satisfied client.