- #1
mr_coffee
- 1,629
- 1
Hello everyone.
I'm currently a Jr. Computer Engineering student. Its funny, you don't really know what a computer engineer really does until your a Jr. and you've already put 2 years. Ever since I was young I loved to program. I always wanted to be a Software Engineer. So when I graduated Highschool I went to a school that offered Software Engineering.
I'm now at a school that doesn't offer software engineering but offers computer science. They are very similar but software engineering also has some business that CS doesn't have. For some reason I never wanted to be a Computer Scientist becuase it was a lot of algorithm analsysi, and doing math proofs, it seems like a math major to me.
So I took up computer engineering because they can take the exact same courses as a CS but also can do hardware courses where a CS isn't allowed to take them or they can but it won't count towards anything but a general education credit, and they also have to take different maths/physics in order to do this.
So it seems like a CS is like a water downed version of a Computer Engineer. I took a circuit analysis class, with just linear devices and I did alright in it, just took a ton of studying.
But when I got to EE 310, which delt with diods, and non-linear devices i was completely lost. The people in the class were EE's and CE's and they loved it and it was so easy to them while I spent hours and hours trying to figure out 1 problem and failed to get it right. I soon found out I couldn't handle taking that class because i spent all day on it and got no where. So i dropped that class as well as EE317, signals and transforms and systems.
I also have tons of trouble with building a circuit and finding its voltage/current/etc, i have no hands on skills it seems.
But I do enjoy programming as long as it isn't recursion, which is another problem. I suck at recursion. If it isn't recursive I can do great, but i know to be a CS you must be good at all aspects, not just some. Thats another reason I went into Computer ENgineering.
If I understood circuits and how to analyzie a circuit (physically) not on paper, i can do it on paper fine, i would enjoy circuits and CE would really interest me. Because then I could get into robotics.
If I'm really terriable at circuit design, should I not be a Computer ENgineer?
Should I be a CS instead even though i suck at recursion and fall alseep when hearing about how many miliseconds this algorithm is faster than the other, blah.
Thanks!
I'm currently a Jr. Computer Engineering student. Its funny, you don't really know what a computer engineer really does until your a Jr. and you've already put 2 years. Ever since I was young I loved to program. I always wanted to be a Software Engineer. So when I graduated Highschool I went to a school that offered Software Engineering.
I'm now at a school that doesn't offer software engineering but offers computer science. They are very similar but software engineering also has some business that CS doesn't have. For some reason I never wanted to be a Computer Scientist becuase it was a lot of algorithm analsysi, and doing math proofs, it seems like a math major to me.
So I took up computer engineering because they can take the exact same courses as a CS but also can do hardware courses where a CS isn't allowed to take them or they can but it won't count towards anything but a general education credit, and they also have to take different maths/physics in order to do this.
So it seems like a CS is like a water downed version of a Computer Engineer. I took a circuit analysis class, with just linear devices and I did alright in it, just took a ton of studying.
But when I got to EE 310, which delt with diods, and non-linear devices i was completely lost. The people in the class were EE's and CE's and they loved it and it was so easy to them while I spent hours and hours trying to figure out 1 problem and failed to get it right. I soon found out I couldn't handle taking that class because i spent all day on it and got no where. So i dropped that class as well as EE317, signals and transforms and systems.
I also have tons of trouble with building a circuit and finding its voltage/current/etc, i have no hands on skills it seems.
But I do enjoy programming as long as it isn't recursion, which is another problem. I suck at recursion. If it isn't recursive I can do great, but i know to be a CS you must be good at all aspects, not just some. Thats another reason I went into Computer ENgineering.
If I understood circuits and how to analyzie a circuit (physically) not on paper, i can do it on paper fine, i would enjoy circuits and CE would really interest me. Because then I could get into robotics.
If I'm really terriable at circuit design, should I not be a Computer ENgineer?
Should I be a CS instead even though i suck at recursion and fall alseep when hearing about how many miliseconds this algorithm is faster than the other, blah.
Thanks!
Last edited: