Bad idea to use the FQDN of the SQL server when running the SharePoint 2013 installation?

I have a customer that found the following article AFTER installing SharePoint 2013 using the FQDN name of the SQL 2012 server during setup.  As you can imagine, they are now concerned.  The profile sync has not been provisioned yet, so my customer does not know if we have a problem or not, but they are concerned.  I would like to calm their nerves a bit.

Here's the article that has created some concern.

http://blogs.technet.com/b/meamcs/archive/2010/12/01/never-again-never-use-a-fqdn-for-the-sharepoint-2010-sql-server-name.aspx

Question: Is it still a bad idea to use the FQDN of the SQL server when running the SharePoint 2013 installation?

Regards,

Mike Griffin - Seattle

Best Regards, Mike Griffin - Seattle