Thanks for having this forum!
It's frustrating to read so often that love of programming is a prerequisite for success. How likely is it for passion to follow competence?
FOLLOW THIS QUESTION TO RECEIVE UPDATES
What is it that you don't enjoy about programming?
Is it trying to remember every little semicolon, function name, parenthesis, etc.? Or do you not like the struggle of finding the right algorithm to solve a coding challenge?
My thoughts are that if it's the first answer then I believe you could grow to like programming once you get past the syntax of whichever language you're learning. It is certainly frustrating to know how to solve a problem, but cannot implement the solution because of small syntatical errors. If it's the second answer however, then I believe it would be much harder to enjoy programming since coming up with efficient ways to solve problems is part of the beauty of programming.
This is how I know who has what it takes in my free workshops. Whenever I make a mistake and have to debug live - which is its own kind of thrill - I take note of the people who are completely fascinated by the process and are almost delighted to see me solve the issue. Then there are those who cannot take more than two minutes of it. They are texting their friends, going on Reddit, catching Pokemon, or doing whatever. These people have no chance as programmers and should quit now. They are also often the ones who ask questions like "so after I learn programming, how much money would I make?" You get the idea.
The people in category B don't understand that they have to compete with those in category A. Category A programs stuff literally for fun and cannot believe they get paid as well. Category A is home on weekends programming stuff, learning a new framework, contributing to open source projects, answering questions on StackOverflow etc - all for FREE. That's category A. Category B doesn't know what Hacker News, StackOverflow etc are and will only learn new things when they have to. That's why they are category B in the first place.
Luckily it doesn't take much to tell which side of the fence you are on. Just watch someone program and see how long you can take it. If you are in category B, consider yourself lucky, it should only take a few minutes to find out.
Velocity 360 is designed for students who want to accelerate their learning through flexible night and weekend schedule. We focus on rapidly growing technologies such as Node JS, React, React Native and iOS. For more information, visit
I think your question is a valid one. A lot of the time we don’t know what we have an affinity for, or what our interests might be until we try things out. It’s like when we were kids, and our parents put food our plate that we were unfamiliar with and immediately, our reaction was “i don't like peas”. We have an aversion for things we have little to no context of. Coding and programming can have a similar effect on people. When you start out, there is a lot of unknown territory. And that time can be filled with uncertainty and discomfort. It does gets easier over time, but you have to first go through that period to get to the other side.
I am pretty new to programming myself. I left Chicago to head west to the land of all things computer science, Silicon Valley. I attended Holberton in the heart of San Francisco, and there are days where I think I am no good at programming and maybe think that maybe i just don’t love it enough. Becoming a good programmer takes perseverance and grit. If there are a few days where you maybe don't love it, I think that is totally normal. Now, if you get to the point where everyday you are dreading opening up terminal or reading one more article on stack overflow, then maybe it's not the right path for you.