The articles states "Generally, developers don't like writing a ton of extra code to add this auditing into their stored procedures and it falls to the DBAs to ensure the auditing is done."

That is the kind of ill-considered statement (and attitude) that drives a wedge between DBAs and developers. A better explanation would be "By putting this code in a trigger, it need not be repeated in every stored procedure and/or dynamic SQL batch that updates the table. Using a trigger also ensures that auding is performed no matter how changes are made (e.g., even by the DBA using Enterprise Manager or ad hoc queries)." Notice how my version does not imply that triggers are only useful because developers are lazy.