Thanks everyone for the replies I see there is a common theme here and i tend to agree that i'd rather not be surprised if something did fill up. 
Instant init is on and also looking at trace flag 1117 as a startup parameter to grow all files in a file group equally. Of course this applies to every database.
For SQL 2016 use AUTOGROW_ALL_FILES option of ALTER DATABASE and do this for tempdb

So I think a little bit of everything is the key.
8 Tempdb data files sized to fill the drive but leaving a margin for monitoring. This way the files should not have to autogrow but can if it gets to that point.
Autogrow at a good size chunk (512 like the first poster mentioned) which would amount to 4 GB total (with trace flag 1117 on or AUTOGROW_ALL_FILES)
Auto file init turned ON
and a log file initially sized at 20% of total with the same auto grow amount. 

What I was looking to accomplish is having a disk config that we can document for our server setups and I think this makes sense.

Edit:
Also include max size of the files set at just under the total space available.