I'm a Second-Year CS Student Building Windows Software. Am I on the Right Track?
hello I'm a second-year computer science undergraduate student from South Korea. Over the past few years, I've been building personal software projects to improve my programming skills. Most of my development experienc
hello
I'm a second-year computer science undergraduate student from South Korea.
Over the past few years, I've been building personal software projects to improve my programming skills. Most of my development experience has come from working independently, experimenting with different technologies, and solving problems as I encounter them.
Recently, I've started wondering whether I'm actually developing the right skills and how my work compares to what experienced developers would expect.
That's why I'm writing this post.
One of My Projects: RamFlow
RamFlow is an open-source Windows memory management utility that I've been developing in C#.
GitHub: https://github.com/homesweetlove/RamFlow
I started this project because I was curious about how Windows manages memory and whether reducing reported RAM usage actually translates into better system responsiveness.
Rather than simply focusing on freeing as much memory as possible, I wanted to explore a foreground-aware approach that considers the applications users are actively working with.
During development, I conducted 1,200 benchmark runs to evaluate different aspects of the project.
However, this post isn't primarily about proving RamFlow's performance.
It's about understanding my current abilities as a developer.
What I'd Like to Know
I've learned a lot through building projects independently, but I haven't had many opportunities to receive detailed feedback from developers outside my university.
I'd really appreciate it if experienced developers could take a look at the repository and share their honest opinions.
I'm especially interested in these areas:
1. Code Quality
Is my code reasonably structured, readable, and maintainable? Are there obvious mistakes or bad habits that I should correct?
2. Software Architecture
Do my design decisions make sense? Am I organizing the project appropriately, or am I making things unnecessarily complicated?
3. Technical Understanding
Does the implementation demonstrate a reasonable understanding of Windows memory management and system-level programming?
4. Engineering Practices
How would you evaluate my approach to testing, benchmarking, error handling, and documentation?
5. Overall Development Skills
Based on this project, what would you say are my strengths and weaknesses?
I'm particularly interested in two perspectives:
- How does my work compare to what you would expect from a second-year computer science student?
- Regardless of my academic year, how far am I from the engineering standards expected of a professional software developer?
Why I'm Asking
I'm not looking for compliments or reassurance.
I genuinely want to know whether I'm spending my time learning the right things.
I know that completing a project doesn't automatically mean the code is well-designed or that I fully understand every technical decision behind it.
That's exactly why I want feedback from people with more experience.
If you notice weaknesses in my architecture, implementation, testing methodology, or general development approach, please don't hesitate to point them out.
Even a few specific suggestions about what I should study next would be incredibly valuable.
Project Repository
RamFlow — Windows Memory Management Utility
https://github.com/homesweetlove/RamFlow
The repository contains the source code and project documentation.
I'd appreciate feedback on the project as a whole, rather than just one particular function.
Thank you for reading, and thanks in advance to anyone willing to share their experience or advice!
Disclosure: I used ChatGPT,cluad to help draft and organize this post. RamFlow is my own project, and the development experiences described here are my own.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.