Horses are powerful animals, and computers are possibly the most powerful thing ever invented. Powerful things in different ways, but somehow we are able to control them.
We should probably not have control of these incredibly powerful things... Who put me in charge?
Riding, as well as coding, takes time and dedication.
If you've ever ridden a horse for more than 5 minutes, you'll know that it certainly isn't as easy as it seems to look. I'll often ache for days after, similar to a very intense workout at the gym. Even if you are just riding at a walk, you are using your abs constantly in order to balance and move with the rhythm of the horse.
Similarly, I used to look at websites and pay no attention to the forms or carousels or pictures that were CENTRED!!
Now I understand how much work has gone into those things.
Horses are very intuitive and can pick up emotion - if their rider is scared, then the horse will wonder why - is there something scary around the corner?! As horses are flight animals, this may end in quite a speedy trip to the floor if you don't get it under control!
However, if you sit comfortably, breathe normally and focus, things will go a lot more smoothly for you.
Equally, if you are stressed or frustrated, the horse will feel that and react accordingly. Like dogs, they aim to please, so they will get upset and frustrated if they feel that they are not making their rider happy.
I rode when stressed once. I was trying and trying to get something right, my coach was pushing me to 'do it again' I tried and tried, and the horse dumped me on the floor. Rightly so! He could feel the frustration from both me and my coach, and probably assumed he must've done something wrong.
I think the same can be said for coding, particularly the staying calm part.
Things will inevitably go wrong if you are stressed, frustrated or tired...
Clearly, horse riding can go wrong - it is one of the most dangerous sports. A bird in a tree, a leaf blowing or a flower growing where it hasn't before can be the difference between a nice gentle walk and a sideways gallop.
Code can also be as illogical and reactive, although the circumstances are often much more controllable. A missing semi-colon, a forgotten capital letter in camelCase, or a typo can make the difference between 'works' and 'broken'!
There are so many things that go wrong with horses - they are actually very delicate and have an incredibly knack of injuring themselves.
Just like with code, they cannot tell you what is wrong, they will just act 'wrong' until you figure out what it is.. it often involves a lot of Googling...
As I mentioned previously, horses are intuitive and will react to what they deem as our illogical reactions, emotions or feelings.
You may have noticed, but people are like that too.
Coding and developing mostly involves working with people, so you must be confident and not allow others to become alarmed at your alarm/lack of focus/frustration.
People will react to how you are feeling.
Generally, the rule 'stay on' is a good one to stick to when horse riding. There are of course, exceptions, such as if your horse is galloping sideways away from a terrifying leaf - you may prefer to 'tactically dismount' (jump off) onto the softer grass you are currently riding on, rather than the hard tarmac you are heading towards..
Sometimes when I ride, everything goes so well that I want to cry with happiness - other times, I declare that I will never ride again and that I hate horses. It's the same with code, right? Some days are good, some days have you declaring you will never do it again!
I think horse riding beats coding here - when you get it right and you are cantering through a field on a sunny day, it's like flying and there's nothing else like it. I haven't quite got there with coding yet, but maybe the time will come..