I've found assigning issues to GitHub Copilot on GitHub itself to be a real step-wise change from one off requests to a chat based interface that has no awareness of my codebase. Maybe it's just me, but I'm getting significantly more realworld value out of AI these days. I've been working through doing an implementation of a spec using GitHub Copilot mostly from my phone, and it has been a really instructive exercise in how to squeeze as much out such a narrow interface as possible. I still dip into a full desktop + IDE from time to time, but for like 90% of it I've been doing it in my phone. Slowly but surely working my way from "vibe coded in a weekend" level initial AI slop quality to nice, clean architecture, excellent dev tooling, production grade multitenant SaaS. I've still got a ways to go, but I'm able to make quite a lot of progress just using my phone during my commute, on my lunch breaks, in between meetings, and bathroom breaks etc.
alt Hacker News
I've found assigning issues to GitHub Copilot on GitHub itself to be a real step-wise change from one off requests to a chat based interface that has no awareness of my codebase. Maybe it's just me, but I'm getting significantly more realworld value out of AI these days. I've been working through doing an implementation of a spec using GitHub Copilot mostly from my phone, and it has been a really instructive exercise in how to squeeze as much out such a narrow interface as possible. I still dip into a full desktop + IDE from time to time, but for like 90% of it I've been doing it in my phone. Slowly but surely working my way from "vibe coded in a weekend" level initial AI slop quality to nice, clean architecture, excellent dev tooling, production grade multitenant SaaS. I've still got a ways to go, but I'm able to make quite a lot of progress just using my phone during my commute, on my lunch breaks, in between meetings, and bathroom breaks etc.