I am ECE student but heavy focus on CE. I have worked on hardware design (gate and transistor level) and software to model and verify the hardware (very high level, C++, Python). I would say for a ECE my SW skills are very good, for CS maybe okayish. For completeness and because I wanted to learn how the device actually does what it should do, I had a classes how compilers work and what an OS, device driver conceptually do but when it comes to truly understanding such things like the actual code of linux OS kernel, Llvm, embedded programming to name a few, my brain turns off. The code is so huge and makes no sense to me and I think I am lacking too much knowledge where generations of SWEs worked on before me. Can one person even learn it (especially when I am already non CS background) just like that or is it a whole life task and I should just stick to my strength in hardware especially when wanting to make a carreer out of that? Like that guy: Writing USB driver for Linux in 3 hours
submitted by /u/MericAlfried
[link] [comments]
r/cscareerquestions I am ECE student but heavy focus on CE. I have worked on hardware design (gate and transistor level) and software to model and verify the hardware (very high level, C++, Python). I would say for a ECE my SW skills are very good, for CS maybe okayish. For completeness and because I wanted to learn how the device actually does what it should do, I had a classes how compilers work and what an OS, device driver conceptually do but when it comes to truly understanding such things like the actual code of linux OS kernel, Llvm, embedded programming to name a few, my brain turns off. The code is so huge and makes no sense to me and I think I am lacking too much knowledge where generations of SWEs worked on before me. Can one person even learn it (especially when I am already non CS background) just like that or is it a whole life task and I should just stick to my strength in hardware especially when wanting to make a carreer out of that? Like that guy: Writing USB driver for Linux in 3 hours submitted by /u/MericAlfried [link] [comments]
I am ECE student but heavy focus on CE. I have worked on hardware design (gate and transistor level) and software to model and verify the hardware (very high level, C++, Python). I would say for a ECE my SW skills are very good, for CS maybe okayish. For completeness and because I wanted to learn how the device actually does what it should do, I had a classes how compilers work and what an OS, device driver conceptually do but when it comes to truly understanding such things like the actual code of linux OS kernel, Llvm, embedded programming to name a few, my brain turns off. The code is so huge and makes no sense to me and I think I am lacking too much knowledge where generations of SWEs worked on before me. Can one person even learn it (especially when I am already non CS background) just like that or is it a whole life task and I should just stick to my strength in hardware especially when wanting to make a carreer out of that? Like that guy: Writing USB driver for Linux in 3 hours
submitted by /u/MericAlfried
[link] [comments]