3 ms·
Same here. It’s fine for me to use the ChatGPT web interface and switch between it and my IDE/editor. Context switching is not the bottleneck. I actually like
by dakiol 1y ago
Same here. It’s fine for me to use the ChatGPT web interface and switch between it and my IDE/editor.
Context switching is not the bottleneck. I actually like to go away from the IDE/keyboard to think through problems in a different environment (so a voice version of chatgpt that I can talk to via my smartwatch while walking and see some answers either on my smartglasses or via sound would be ideal… I don’t really need more screen (monitor) time)
- DoesntMatter22 1y agoMan that workflow is brutal
- divan 1y agoI use voice mode of ChatGPT almost exclusively using RayBan metaglasses(especially when outside / cyciling).
- jjani 1y agoYou would like to, or you're actually doing that right now?
- johnisgood 1y ago> Same here. It’s fine for me to use the ChatGPT web interface and switch between it and my IDE/editor. I do this all the time, and I am completely fine with it. Sure, I need to pay more attention, but I think it does more good than harm.
- CuriouslyC 1y agoSorry to say but this workflow just isn't great unless you're working on something where AI models aren't that helpful -- obscure language/libraries/etc where they hallucinate or write non-idiomatic solutions if left to run much by themselves. In that case, you want the strong human review loop that comes from crafting the context via copy paste and inspecting the results before copying back. For well trodden paths that AI is good at, you're wasting a ton of time copying context and lint/typechecking/test results and copying back edits. You could probably double your productivity by having an agentic coding workflow in the background doing stuff that's easy while you manually focus on harder problems, or just managing two agents that are working on easy code.