At age 37, I feel young and really wish that I will still be able to program at age of 50 and beyond.
532 karma · joined March 29, 2013
At age 37, I feel young and really wish that I will still be able to program at age of 50 and beyond.
After that, you need hours and hours of practice in order to be good at it. We learn by doing.
There is also a contingency plan for students who come from families with a household income of R600,000(USD 43,000) per annum.
I graduated last year September at the age of 36 and I am no longer considered an IT dropout or self-taught Programmer. Reason I decided to go back to school was because I was always considered a self-taught Programmer, even though I was taught programming in a formal qualification which I didn't finish. The fact that I finished all programming related modules and was only left with 3-4 Electrical Engineering related modules, didn't help.
Studying when you are older is easier because you are doing it with a purpose. Plus when you are older, you spend more time at home and party less. Freeing more time for studying. The course I did, was heavy in programming, mobile app development and web design. Something I have been doing for over 10 years before I decided to go back to studying.
After having some success in the gym using this technique, I decided to try it for my studies. I enrolled for a 3-year IT qualification and managed to finish it in record time while working a full-time job and running a profitable side project.
I was doing 5 modules every semester. Every weekday when I wake up, first thing I did, was taking a shower and study for an hour, then go to work. I was studying just one module per day.
This year, I am planning to study further using same technique. I always recommend this technique for people who think they don't have time to do X. The best time to do X is always first thing in the morning when there are no distractions.
2. Xamarin Forms because my new job requires it
3. UX Design because I want to improve usability of my systems
4. Software Project Management because I want to move to management
These days I try to avoid learning new technologies. I focus mostly on improving what I already know. I only learn a technology when I want to use it and there will be a benefit for using it compared to what I am already know.
While writing this comment, I was reminded of a verse in the bible that tells Chrstians to 'seek the kingdom of God first and the rest will follow'.
This is the strategy that I prefer. I aim to deliver version 1 of my side projects within 3-4 weeks. After working on it for too long without delivering, I lose interest. I fix the time and budget of the version, not the scope. Unfinished features are cut out of the version 1. I focus on the core features. There will always be time to add extra features in the future.
Most people are afraid of launching because they don't want to be judged. That's why they delay the launch. I prefer giving my software to a handful of real users as soon as possible. So that they can test and give me feedback. There will always be bugs in software. Show me a popular software product and I will give you a list of over 10,000 bugs which were reported in its lifetime. What matters is the speed in which you fix them. If you created version 1 of the product, you wouldn't waste more than a day fixing all bugs reported on first day.
'Great artists ship' - Steve Jobs.
South Africa is very a profitable country to the West, not the other way round. It was even more profitable during the dark days of apartheid. That's why USA was sponsoring apartheid government with intelligence and arms. Google about Mandela arrest and CIA's involvement. They even listed Nelson Mandela as a terrorist. Even when he was President, he was still listed as a terrorist. US only removed him from the terrorist list few years ago.
I live in South Africa.
'The best time to buy is when there is blood on the streets' - Baron Rothschild.
The only aid we need is for Western countries who sponsor African wars to stay away from Africa. I have been living in Africa since birth(35 years old). I have never seen anyone dying of hunger.
Another thing I have noticed is that a chapter about usability of websites is treated as an extra. Usually at the end of the book as additional reading. Maybe we need to regulate the industry and make it impossible for people to start practicing without proper training. There are codes of conduct that a lawyer, accountant or doctor has to abide to, but there is none for a Website Designer. No implications whatsoever for not making websites to be accessible. They end up blindly ignoring accessibility because they weren't trained to do it.
Fining companies won't help because 99% of the companies are headed by people who don't need to know if the website is accessible to the blind or not. They just trust the designer to do a good job. The only time they will know they are supposed to make their website to be accessible is when they are getting sued. Problem is that regulation will greatly reduce number of practitioners and greatly increase the cost of website development.
Speed of development greatly improved since I switched to EF. Speed of development is what matters most for me when building first version of an application.