I'm 15 and plan to formally enroll in a computer engineering program next year. I'm currently completing prerequisites at a community college and have studied the basics of C, Go, C++, and x86 assembly. The problem is that I understand syntax and small examples, but I don't feel confident building anything useful on my own.
I'm interested in operating-system development, ethical security research, and mobile development. I'd like to work independently alongside my private tutoring, but I can't use Discord, so I'm looking for other ways to learn and find project ideas. What beginner-friendly projects would help me build practical skills, especially projects related to OS development? I'm currently using an M2 MacBook, although I'll soon have access to an older 16 GB laptop and a more powerful Xeon-based development machine. I'm considering experimenting with FreeBSD, Plan 9, or another operating system.
Would it be better to focus on computer science fundamentals at home and rely on university mainly for computer engineering, or should I structure my self-study differently?
3 Answers
The best way to improve is to choose a small problem you actually care about and build a solution, even if it seems simple. For example, you could make a small program that monitors a Bluetooth device and triggers a light or another output when you arrive home. Projects like that force you to learn the pieces you’re missing— APIs, hardware interaction, debugging, and system design—instead of just memorizing language syntax. Start small, finish something, then gradually add features.
Try not to choose a project just because it sounds impressive, such as writing an entire operating system or jumping straight into security research. Pick a narrow milestone: write a command-line utility, implement a small data structure, build a toy shell, create a simple network client, or boot a minimal kernel in a virtual machine. Once one project works, improve it with tests, documentation, error handling, and one new feature at a time. That process will reveal what you need to learn next much more effectively than studying languages in isolation.
Don’t worry too much about the processor architecture you’re using. ARM is a capable and widely used architecture, and the M2’s limitations are mostly about macOS tools and compatibility rather than ARM itself. You can use virtual machines, cross-compilers, containers, or another computer when you need an x86 environment.
For OS development, begin with a very small kernel that boots in an emulator, prints text, handles basic input, and eventually manages memory or simple processes. There are plenty of beginner OS-development tutorials and emulator-based workflows for this. FreeBSD can be useful for learning about a mature Unix-like system, while Plan 9 is historically interesting, but neither is required for learning the fundamentals. Linux and small educational kernels may provide more examples and tooling.
More importantly, knowing several languages does not automatically teach CPU architecture, operating-system design, networking, data structures, or debugging. Treat programming languages as tools and deliberately study those underlying concepts while applying them to projects.
That makes sense. My frustration is less with ARM itself and more with macOS being restrictive and some open-source tools assuming an Intel or AMD environment. I appreciate the advice.
Exactly. Build around problems you personally encounter. A simple finished project will teach you more than an ambitious idea that never gets completed.