I find it easier to visually process what's going on if you use enter find mode, set field, perform find. That's a good thing when passing it on to other developers. I find the specify find dialog box to be a little kludgy, but that's complete personal preference.
Also, by using:
Enter Find Mode
Go To Layout
There is a noted speed increase vs.
Go To Layout
because the data is not loaded from going to a layout in browse mode, especially on list and table views. (yes, data is still loaded even if you use freeze window). This can have a huge effect when you're doing multiple finds inside a loop for things like reporting.
I am with Mike on the idea that readability greatly outweighs having fewer lines of code. And really, fewer lines spawns many lines of comments to explain a complex multipart search routine.
"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live." `John Woods
I've made it a practice to enter Find mode before Go to Layout wherever it's feasible, for the reason you said, Mike. A recent discussion put forth the idea that Freeze Window in FM13 would do the job -- but I'd love a more definitive source.
"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live."
Now that's funny ...
As has been stated by others, make easy to see what is going on. So I use set field.