GyroVorbis wrote:Pft. DON'T take it easy on yourself. Don't rely on school to teach you things (because it won't teach you a tenth of what you want to learn). Don't ever stop pushing or fighting to better yourself when it comes to your potential. There is nothing nobler than striving to be better. Be your own teacher and take a proactive stance on your education. That's the only way to make it in a field as large as this one.
What have you gotten out of your college education with a computer engineering degree? It seems you learned most of the things you know by yourself and not learn as much from school.
It's true. I learned virtually nothing about software. I learned that I "knew" enough to have a software engineering/computer science degree before I went in...
But I have to admit that everything that I know about analog and digital circuitry, I learned from school. That's why I chose computer engineering over computer science. I spent all of my free time becoming a programmer/software engineer. I figured that I could at least learn some hardware while I was in college.
GyroVorbis wrote:Pft. DON'T take it easy on yourself. Don't rely on school to teach you things (because it won't teach you a tenth of what you want to learn). Don't ever stop pushing or fighting to better yourself when it comes to your potential. There is nothing nobler than striving to be better. Be your own teacher and take a proactive stance on your education. That's the only way to make it in a field as large as this one.
Okay, since you obviously know more about this than me I will take the part about taking it easy back(It was not my main point though). But isn't measuring your C++ experience in the amount of GUI library calls you know and your SQL experience in the amount of statements you know a completely wrong way to look at things?
What my main point is, is that you should work on something you find challenging and fun/interesting(I think it is a common trait for programmers that they find challenges(programming related ones at least) fun/interesting). Not thinking about what functions in what library you may or may not need when you at some point start on a job.
Again, i have no experience to back any of this up with, so i might still be completely off.
ismetteren wrote:
What my main point is, is that you should work on something you find challenging and fun/interesting(I think it is a common trait for programmers that they find challenges(programming related ones at least) fun/interesting). Not thinking about what functions in what library you may or may not need when you at some point start on a job.
While it is true that one should not dwell on which language, API, or function one chooses, without knowledge any programming tool how can one seriously present oneself as a programmer?
Falco Girgis wrote:It is imperative that I can broadcast my narcissistic commit strings to the Twitter! Tweet Tweet, bitches!
