Thanks for compliments.
The main reason, as @geniusintraing stated first, is that I learned, both through trial and error and then instruction, outputs last! It is likely you will have more than one condition to turn on an output...so if you turn it on in rung 5 and then realize later in the logic you need it on again because of a reset sequence...things can get confusing..both for you and anyone that needs to get into the code later.
I was brought up in the SLC500 world when I learned programming and if you had the same output in 2 or more places in a program, then only the last one worked. The newer stuff (contrologix, etc.) can maybe do this?
I've programmed a fair # of machines using this type of "step" method...it's made sense to my simple mind and I've found it easy to navigate and find where/why machine is stuck as have maintenance personnel that I have reviewed it with.
I don't think there is one right way...every machine is different as is every programmer. Find what makes sense for you.
Where I am know I am a Machine Tester...verify custom equipment meets customer specs., debug, find issues (mechanical, electrical, program) and the controls group here programs in State Logic (if step done, then move 10 to state, if = 10 then do something, when done move 20 and so on)...I hate it! Though it really isn't that different than what I am doing.