Yes, 10% growth is a horrible setting as well.
Try to grow with fixed size chunks of 256MB-1024MB instead (depending on your database growth expectation).
For log files, set an upper limit and never ever let a log file grow indefinetly! Transactions need to be short and if some screw up code runs out of control, you want a hard limit to stop it before it fills up all your storage and crash your server (talking simple recovery model here).
What is true for logfiles is true for tempdb as well, limit its size, but you can be generous there (10-20GB)!
These are (my) rules of thumb and i review them per database i deploy, every case can be different! It is not something you can script with always a good outcome.