UPHILL DOWNHILL: STOP AND GO
If you ever travelled then you have probably had do travel uphill and downhill. You have also noticed that the speed changes. Downhill seems to make the vehicle go fast and uphill makes it go slower. If you have been lucky to travel through a road that is under construction or undergoing rehabilitation, then you have probably been through a stop and go. A very familiar thing to many South African since our roads always need rehabilitation every 'week'. Thank you cadre deployment for the constant stops and go. Jokes aside, let's carry on.
With programming, the journey carries some similarities to elevation changes as well as stop and gos. Each project or exercise will have its own up and downs. Some will be major and some will be minor. Some of them look minor till you are midway through them and start losing momentum. Do not expect to ever master everything to get to a point of freely riding through it all. Expect days where things will go very slow. And days when things happen so fast. But for both, always move forward with caution. Too much speed may lead to a crash. Speed kills. Losing momentum may also lead to rolling backwards. Slow speed kills too.
But the one I want to focus on much is the stop and go. This happens very often when you start off. It is what separates those who give up from those who go on to be great developers, as my mentor likes to put it. There will be times where you will hit a wall, and will have to stop. There are days where you will feel completely clueless. When this happens, do not give up and say it is impossible. This is the part where you start seeing the beauty of programming. When there's no way of doing something, you create it. And that is how we get all these beautiful and useful libraries that aid us in doing things quicker. When you get to a stop and go, do not turn around and say my journey has ended. Soon it will flash go(by flash I mean the guy will turn the sign around to show 'GO'.
Sometimes though, you just need a toilet break or a coffee. Most of my programming problems where solved on a toilet seat. Creepy I know, but sometimes I just go and sit on it and think hard. But everyone has their own way of dealing with things.
Happy Coding
Mbuelo Ramafamba
With programming, the journey carries some similarities to elevation changes as well as stop and gos. Each project or exercise will have its own up and downs. Some will be major and some will be minor. Some of them look minor till you are midway through them and start losing momentum. Do not expect to ever master everything to get to a point of freely riding through it all. Expect days where things will go very slow. And days when things happen so fast. But for both, always move forward with caution. Too much speed may lead to a crash. Speed kills. Losing momentum may also lead to rolling backwards. Slow speed kills too.
But the one I want to focus on much is the stop and go. This happens very often when you start off. It is what separates those who give up from those who go on to be great developers, as my mentor likes to put it. There will be times where you will hit a wall, and will have to stop. There are days where you will feel completely clueless. When this happens, do not give up and say it is impossible. This is the part where you start seeing the beauty of programming. When there's no way of doing something, you create it. And that is how we get all these beautiful and useful libraries that aid us in doing things quicker. When you get to a stop and go, do not turn around and say my journey has ended. Soon it will flash go(by flash I mean the guy will turn the sign around to show 'GO'.
Sometimes though, you just need a toilet break or a coffee. Most of my programming problems where solved on a toilet seat. Creepy I know, but sometimes I just go and sit on it and think hard. But everyone has their own way of dealing with things.
Happy Coding
Mbuelo Ramafamba
Comments
Post a Comment