| General > General Technical Chat |
| Starting a new CompSci/Electronics career -need advice! |
| (1/14) > >> |
| x_marx:
I have been working as a Design Engineer for a machine manufacturer for like 10 years. I do CAD stuff (I'm a Mechanical Engineer btw) and plant design (mainly machine capacity calculations, layouts and process logic). But, I have always loved CompSci and electronics. Love tinkering with stuff with my fav being audio DACs. I'm also into LEDs and lighting. So, I joined an MSc course in Computer Science and learned a lot of C# and zero hardware stuff which I'm not a big fan of. It's too modern for me lol :D I would rather have C :P and a lot more hardware stuff. So, for a 'fresher' like me, is it a good idea to go for C+embedded at this stage? Regards Max |
| RoGeorge:
CS (Computer Science) is about software. EE (Electrical Engineering) is about hardware. If you want to do programming, then continue with CS, otherwise for electronics and hardware you may want to switch to EE MSc. |
| SiliconWizard:
If you're more into low-level and hardware stuff, EE is probably the way to go here. CS will definitely be too software, and *modern* software-oriented. And not just for your courses. Beyond that, once you have a MSc in CS, you'll mostly find jobs were you'll be expected to do C#, Java, maybe some Python, maybe some C++ (maybe), or even uh... worse, web development stuff. Something that, from your short description, you're probably not going to enjoy. But we're talking about enjoying what you do here. Pure software would probably be a better option if what you care about is finding good paying jobs easily. |
| x_marx:
--- Quote from: RoGeorge on September 03, 2022, 04:49:17 pm ---CS (Computer Science) is about software. EE (Electrical Engineering) is about hardware. If you want to do programming, then continue with CS, otherwise for electronics and hardware you may want to switch to EE MSc. --- End quote --- In our Mechanical Engg. course, we had to study C basics along with C graphics and mathematical modelling using C (fast Fourier transforms and stuff). I really loved it so much that I got perfect scores in all of them. My examiners were sceptical about how I achieved coz my scores in other subjects were average. It's that experience that I had me believe I can do well in modern languages. Since this course is about to finish, I'm not sure I can switch. Also, I have a family and my partner is not currently working. Have to support them financially. So, I was exploring the idea to brush up on my C and try some embedded dev using C. But, my friends say the barrier of entry in embedded stuff is rather high and the pay is relatively low. I do not mind the pay part but worry about the barrier of entry part and hence my question. --- Quote from: SiliconWizard on September 03, 2022, 08:32:59 pm ---If you're more into low-level and hardware stuff, EE is probably the way to go here. CS will definitely be too software, and *modern* software-oriented. And not just for your courses. Beyond that, once you have a MSc in CS, you'll mostly find jobs were you'll be expected to do C#, Java, maybe some Python, maybe some C++ (maybe), or even uh... worse, web development stuff. Something that, from your short description, you're probably not going to enjoy. But we're talking about enjoying what you do here. Pure software would probably be a better option if what you care about is finding good paying jobs easily. --- End quote --- Yeah, this course is really modern! We study software engineering, android app development, 'serious game' development using Unity, and C#. As part of the coursework, I had to learn ASP .Net MVC and it was not that bad. I might learn the Razor pages development to become a proper dev in ASP dot Net 6. But yeah, my passion is elsewhere! Can I study embedded development part-time and be hopeful of landing a job in that field? What do you guys think? |
| tggzzz:
I'm not going to comment on the absolute probability of getting a job, since I'm too long out of the market. To increase the probability, it is useful to demonstrate your command of both theoretical and practical aspect. Both are necessary, neither is sufficient. The way to do that is to do a "difficult" home project. Don't simply state, but demonstrate: * you do more than necessary to get the degree, because you like the subject (and by implication will enjoy working for them). That puts you ahead of most people * perseverence and achievement * you can choose projects that aren't easy, but which are possible * what challenges you set yourself * what unexpected problems you had when designing, implementing and testing the project * what you got right * what you would do differently next time. Looking out for better ways to do things in the future and learning from your experience are valuable attributes * your honest assessment of the project, good and badNote that the choice of the project is up to you. Being able to select realistic "stretch" goals is an important skill. You'll also have something to talk to the interviewers about - and sometimes it is good to find anything a candidate can talk about! Good luck and "have fun, safely". |
| Navigation |
| Message Index |
| Next page |