3 ms·
It took me a long, long time until I became reasonably confident that most problems would eventually succumb to my programming ability. Probably almost twenty
by patio11 16y ago
It took me a long, long time until I became reasonably confident that most problems would eventually succumb to my programming ability. Probably almost twenty years from when I wrote my first program, or a few years after college.
I can't write code on my own, though -- unless the problem is trivial and the APIs I'm using I know like the back of my hand, I need an Internet connection to do it.
Part of this issue is possibly that competent people are disproportionately stalked by the worry that they're secretly incompetent.
- donaq 16y agoThat is interesting. The experience has been almost the opposite for me. When I first started programming, it did not take me long to start "getting it", and I was very confident that there was no programming problem I could not solve. As the years went by, I've noticed that my confidence has decreased to the point where I am almost certain that there is no problem I can solve (besides the most trivial ones). Maybe I'm just getting dumber.
- sga 16y agoAbsolutely not. As you gain domain knowledge you should feel exactly this way. I'd suggest that you be concerned if you didn't feel this way. When I finished highschool I thought I was pretty damn smart and had a lot of things figured out (clearly not the case). From an academic point of view as I worked towards my Ph.D. I was constantly reminded of how very little I did know. While I did learn new things day by day, my appreciation for how much I didn't know grew exponentially. In fact I think what I'm left with after the whole exercise is not a confidence in my knowledge but rather a confidence in my ability to learn, problem solve and ask questions.
- 7402 16y ago"Universities are repositories of learning because students enter knowing everything, and leave knowing nothing."
- crgwbr 16y agoI'm the same way about needing an internet connection- or at the very least a nice thick book referencing the APIs. I'm sure if you use the same API everyday the reference wouldn't be necessary, but that's not true of most of the stuff I do. It be interesting to see what the numbers are of people who need to be connected versus people who code in solitude.