I don't see using the proper process as any slower. It reduces the activation energy needed to make changes when you know you can revert them no matter how mess

I don't see using the proper process as any slower. It reduces the activation energy needed to make changes when you know you can revert them no matter how messed up, as well as deploy it live by simply pushing master to origin. The main threat after not building something useful is having the code and design go off the rails, a standard git process prevents it. You can handle almost any complexity without getting confused about the state of things.