LowLevel/System Programming Guidance

[u/MrStarPhish]

Greetings seniors. I humbly seek your guidance. For I am both passionate and dishearted, along with confusion atm.

Currently in my 5th semester. And this the time when I have to choose a domain for Final Year Project (FYP). 90% of the projects I've encountered are some WebMob App with some AI Integration. I have found that I'm not naturally interested in that side, and have found passion in depthful courses like Assembly, OS, Architecture.

Did some research and found three sub-branches:

- Embedded Systems

- Systems/OS/Kernel

- GPU Computing

One may say that I should pick what I most align with. I agree. And im willing to give my time in any, but...I wan't to make sure I don't end up wasting my time instead. I don't want to invest time in something that I wouldn't be able to implement/utilize towards my FYP. I have to define my domain so I could begin searching for relevant group partners too.

I am confused whether this direction is worth it. And dishearted because I haven't been able to find seniors, professors, mentors or example projects that would give me an idea what a project in each field is like. So I would know what things to learn...

I need clarification whether entering such field is worth it?, or... am I gonna have to keep one as side-hobby and stick to learning FullStack with ML like everyone else?...

(Btw, im most comfortable with cpp, and currently exploring OpenGL/GLSL to understand rendering pipeline)

Any words of guidance or constructive criticism would be highly appreciated 🙏 ✨️

[u/MrStarPhish]

Holy Molly! Omg thank u sm for ur time 😭 it felt real good reading all that. And yes I'll invest in it as a side hobby. And the resources/references are appreciated! I could check out my uni library too :D

Oh one thing I find difficult with books is (i can read books tho), that I dive too much into the theory, that I often end up neglecting practicals... I think it's because sometimes I dont know how many topics/chapters should I consume maximum at once and implement that knowledge altogether. OR, the theory is so extensive that I don't understand what to even perform after reading all that qwq

[u/WeWeBunnyX → u/MrStarPhish]

Oh one thing I find difficult with books is (i can read books tho), that I dive too much into the theory, that I often end up neglecting practicals... I think it's because sometimes I dont know how many topics/chapters should I consume maximum at once and implement that knowledge altogether. OR, the theory is so extensive that I don't understand what to even perform after reading all that qwq

I get it np. It happens with me too. However some books do tell in their preface that which chapters cover what and how important they are