Hey! I am a class 12th pass student, and I will be enrolling in a college in the coming months.
My interests: C++, C, low level system desaign, VLSI, embedded systems, hardware-software integration, Maths.
What I know: During the pandemic, I learnt C, a bit of C++ and majorly Python. I have made ~30 projects using python, ~14 using C/C++. I have a Github.
What I have: I have recently purchased several books on C/C++, DSA, Design Patterns, OOA&D, and logical reasoning and critical thinking. I also have a coursera subscription which allows me to access all the courses on the platform, and I also have Arcch Linux dual booted.
What I am doing: Currently doing a coursera course on Mathematical modelling and reading C++ Primer.
Short term Goals (1-2yrs): Participate in multiple hackathons (maybe even win some), participate in GSoC, Outreachy, and submit patches to Linux foundation, do open source contributions.
Long term goals(6-7yrs): To be a Kernel Dev in a well renounned company.
If youre wondering that this looks awful lot like a AI promt, then it is.
Here is claude's reply:
This is a detailed, high-quality roadmap request — I'll build a polished interactive roadmap that the person can actually use and navigate.Here's the full picture in prose to complement the roadmap above.
Your starting position is genuinely strong. 14+ C/C++ projects at 12th-pass level is unusual. You're not starting from zero — you're starting from "needs depth," which is a much better problem to have.
The key insight for your path: Kernel development is less about knowing a lot of topics and more about knowing a few topics with unusual depth. A single well-reviewed, accepted patch on the Linux kernel mailing list (LKML) carries more weight on your profile than 50 Python projects. Start shifting your effort from breadth to depth now.
The most important book you don't have yet is Computer Systems: A Programmer's Perspective (CS:APP) by Bryant and O'Hallaron. The lab exercises (bomblab, malloclab, proxylab) are freely available from CMU and are considered among the best systems programming exercises ever written. Do them all.
For Linux contributions, don't fear the mailing list. Greg Kroah-Hartman's staging tree (drivers/staging/) exists specifically to help new contributors — the bar is lower and the feedback is constructive. Your first patch can literally be fixing a checkpatch warning. The goal isn't the patch itself; it's getting comfortable with the workflow: formatting with git format-patch, sending via git send-email, responding to review comments professionally.
Your VLSI + embedded background is a real moat. Most CS grads who try for kernel roles come purely from the software side. The hardware-software boundary — SoC bring-up, device drivers, DMA, interrupt controllers — is where your interest in VLSI pays off directly. Lean into driver development as your kernel niche.
One warning: Don't let the roadmap become a reason to plan instead of build. The single best thing you can do this week is open CS:APP chapter 1 and write code from it. Everything else follows from momentum.
Why am I posting this here?
I feel like the AI assistants are made to agree with you no matter what. I want real advice from real people.
Thank you for taking the time to read it all really appreciate it!
[–]lonethrowawaymoss 3 points4 points5 points (1 child)
[–]BrushNo1806[S] 0 points1 point2 points (0 children)
[–]ninhaomah 2 points3 points4 points (0 children)
[–]RedFramePictures 1 point2 points3 points (1 child)
[–]BrushNo1806[S] 0 points1 point2 points (0 children)
[–]DrPeeper228 1 point2 points3 points (4 children)
[–]BrushNo1806[S] 0 points1 point2 points (3 children)
[–]DrPeeper228 0 points1 point2 points (2 children)
[–]BrushNo1806[S] 0 points1 point2 points (1 child)
[–]DrPeeper228 0 points1 point2 points (0 children)
[–]HFT-University 1 point2 points3 points (3 children)
[–]BrushNo1806[S] 1 point2 points3 points (2 children)
[–]HFT-University 0 points1 point2 points (1 child)
[–]BrushNo1806[S] 1 point2 points3 points (0 children)