I'd have thought that what the article refers to as "coding architect" would be a dev lead in many organisations, and the role of "knowledge-sharing architect" is the traditional software architect role, i.e. someone who comes from a coding background and understands code well but isn't one of the core developers (so doesn't risk getting lost in the details, becoming a bottleneck, etc.).