There is a specific point in every developer’s journey where you stop just "writing code" and start managing the entire repo cos you're just a solo developer. For me, that happened when I stopped thinking about my "to-do" list and started using the GitHub Issues tab to plan whatever repo I was working on Apparently, I understood Pull Requests and Merges before Issues cos I never tried to understand it's purpose fully; but today I decided to give it a serious try. I used to think Issues were only for massive open-source teams, but even as a solo developer, using an Issue-driven workflow has changed the game: 1. The Technical Debt Trap: I caught a loop that was running infinite times and was about to cook my PC. I simply created 'Issues' regarding it and plus the other problems in my code. 2. The CLI Advantage: I am in the habit of using the GitHub CLI (gh issue create) for most of my work (like pushing code, commit message). Command Line Interface makes it quite easy to do so. 3.…