I like to think a great engineer is also not afraid to write some iffy code in 1/10 the time if it solves 90% of the problem and not be bothered by the code being not to pretty.
The trick is to know the bounded context of the "iffy-ness". Iffy code that might occasionally lead to latency or a timeout for some users using your service, is different from iffy code that charges the user the wrong dollar amount at checkout, or iffy code that could brick a user's device. Great engineers know which things are safe (enough) to take what types of shortcuts on.