Harshil Patel

Nov 28, 2024 | dev.to | Harshil Patel

This is the final blog in my three-part series where I share my experience contributing to the Node.js core repository. In my previous blogs, I detailed how I identified an issue, tested it locally to confirm its existence, and opened a pull request (PR) with the necessary changes.

Nov 27, 2024 | dev.to | Harshil Patel

This is the second blog in a series of three, where I am sharing my experience contributing to the Node.js core repository. You can read the previous blog here: Contributing to Node.js: Improving Test Runner Coverage Reporting. In the previous blog, I discussed how I discovered the issue and confirmed that it exists in Node.js. After that, I forked and cloned the Node.js repository and opened it in VS Code.

Nov 24, 2024 | dev.to | Harshil Patel

IntroductionHi! My name is Harshil. I am currently enrolled in the Open Source Development course at Seneca College. In this course, we are required to contribute to different open-source repositories every week. So far, I have contributed to more than 10 issues across 6+ open-source repositories. You can find the full list of my contributions here: .

Nov 23, 2024 | dev.to | Harshil Patel

Hi my name is Harshil and if you have read my previous blogs then you know that I am working on a Command line tool called resume-enhancer. ResumeEnhancer is a command-line tool that uses AI to optimize your resume for specific job descriptions. Input your current resume and job description, and it will suggest changes to highlight relevant skills, experience, and certifications without adding false information. It helps tailor your resume to increase your chances of getting hired.

Nov 20, 2024 | dev.to | Harshil Patel

First PRThis blog is about the two PRs I made this week. If you’ve read my last blog about my contribution to ChatCraft, where I worked on the Ask and Retry menus, you’ll know that I contributed a reusable component for those menus. While working on that issue, I discovered a bug. The bug occurred when you retried a response—sometimes the request failed on the LLM side, but no error message was displayed on ChatCraft when it happened.