Triggers are not something that are in our control. If I have 5 triggers on the same event for an object, I will never be able to control the order of execution of these triggers. 

So as suggested in the posts above, have one trigger one object. And use apex classes as handlers where all the logic stays. This way you can always re-order your methods in the apex class to control the order. 

Example:
My trigger:

Trigger sampleTrigger on Contact(after insert){
     ContactTriggerHandler cth = new ContactTriggerHandler();
     if(Trigger.isInsert && Trigger.isAfter){
           cth.OnAfterInsert(trigger.new);
     }
}

And my handler class:
public class ContactTriggerHandler{
     public ContactTriggerHandler(){
     }
     
     public void OnAfterInsert(List<Contact> newContacts){
     // call method 1 : 
     updateSomeFieldOnAccount();
     // call method 2 :
     updateSomeFieldOnOtherObjectBasedOnUpdateAbove();
     } 
}

So in my onafterinsert method above, I am calling two methods - each having some business logic. 
So idea is, I want to update some data based on some update I perform on Account. If I have two triggers then it may happen that the one which updates some object data may fire before the one that updates the Account. 

In apex, I can re-order my methods as per my requirement and hence this is a much better way of writing triggers. 

Hope this helps you :)