Monthly Review: June 2025 – A monthly Journey in Learning and Tech

Introduction

June was a month rich with new lessons, technical breakthroughs, and personal projects. I doubled down on system programming (especially Rust), worked on coding tasks, polished side projects, and found inspiration in both challenges and little wins. Here’s a day-by-day breakdown of my journey, with a special focus on learning and professional growth.

June 1-3: New Month, New Focus

• Kicked off my month with planning: set technical and learning goals for both Rust system programming and web projects.

• Organized my notebooks and folders for clearer sprint tracking (I track my activity using notion which I have sprint for every month).

• Read about the “criteria for local problem oriented software” a recurring theme throughout the month, reminding me of the need for context-first solutions.

• Explored mentor resources from the Rust community, especially from the Awesome Rust Mentors list.

June 4-7: Rust Deep Dive & Applications

• Spent this time on Rust fundamentals: ownership, borrowing, and lifetimes.

• Worked through practical tasks, like writing code samples for device drivers and simple error handling.

• Submitted several applications for developer roles.

• Kept reading technical articles and Rust blogs to reinforce my knowledge.

June 8-10: Building OS from scratch khwajalabs.com course

• Began working on lower-level system programming, such as implementing inter-process communication (IPC) and building basic system calls.

• Learned about debugging techniques for kernel development, from segment faults to memory isolation. My notes emphasized the “why” behind each layer in OS development.

• Spent time on the OSDev Wiki and “Make a Simple Operating System” guide to reinforce key concepts.

June 11–14: Project Week & Documentation

• Started and make little progress on my “SmartStock - Coding Tech” project, focusing on alert systems and expiry calculations.

• Improved my CSS and interactivity skills, updating my portfolio with new effects and accessibility features.

June 15–18: Career & Community

• Reflected on my involvement with developer groups (notably GDSC and Facebook Developer Cycle), the value of networking was a key takeaway.

• Reached out to Rust mentors for feedback on my learning path.

June 19–22: Building & Reviewing

• Continued coding in Rust, focusing on topics like device drivers, error handling, and security.

• Evaluated and improved my Github profile and explored modern practices for open-source collaboration.

• Maintained a habit of tracking all activities (including learning, project builds, and job search) in a daily log.

June 23–26: Side Projects & Knowledge Sharing

• Dived into TypeScript and React, especially on adding interactivity and best practices for state management.

• Learned about new compiler features in React that enable finer-grained UI updates, sparking ideas for future side projects.

• Set aside time to read widely: from OS architecture to broader technical trends (Docker, cloud, and more).

June 27–30: Review & Reflection

• Wrapped up the month by reviewing sprint achievements and technical takeaways.

• Finalized and shared my notes on system programming, especially kernel debugging techniques and building secure components.

• Caught up on movies for both fun and inspiration, including “Wolf of Wall Street”, “Secret Level“ and “Storks.”

Key Lessons & Progress

• Rust’s ownership/borrowing model taught me to be more deliberate and thoughtful in how I manage software resources.

• With the help of khwajalabs.com building minimal operating system components boosted my confidence and “engineering humility” as every bug is humbling!

• Technical side projects like SmartStore improvements were practical laboratories for theory and hands-on skills to meet.

• Networking and community engagement kept me motivated and accountable.

Conclusion

June was an intense but rewarding month. The combination of daily coding, structured technical learning, reaching out to mentors, and logging both successes and frustrations helped me stay on track. My key advice to anyone pursuing a similar path: stay curious, iterate quickly, and don’t hesitate to reach out for help. Here’s to even more growth in the months ahead!

Disclaimer

AI is used in writing this. It is used for grammer and spelling checkings and thumbnail creation.