Re:Claude Code is suddenly everywhere inside Microsoft
by mimischi on Monday February 02, 2026 @03:20PM
(#46860891)
As an aside: have you thought about using agent-shell?
Re:Claude Code is suddenly everywhere inside Microsoft
by superfrank on Monday February 02, 2026 @01:20PM
(#46859284)
> I work on a story by splitting it into small steps
It's funny because that's basically the approach I take in GH Copilot. I first work with it to create a plan broken up into small steps and save that to an md file and then I have it go one step at a time reviewing the changes as it goes or just when it's done.
I understand that you're using emacs to keep an eye on the code as it goes, so maybe what I wasn't groking was that people were using terminal based code editors to see the changes it was making. I assumed most people were just letting it do it s thing and then trying to review everything at the end, but felt like an anti-pattern given how much we (dev community) push for small PRs over gigantic 5k line PRs.
Re:Claude Code is suddenly everywhere inside Microsoft
by 1899-12-30 on Monday February 02, 2026 @01:23PM
(#46859321)
have you tried the emacs package agent-shell?
Re:Claude Code is suddenly everywhere inside Microsoft
by PantaloonFlames on Monday February 02, 2026 @02:41PM
(#46860289)
yes, similar.
Re:Claude Code is suddenly everywhere inside Microsoft
by bluGill on Monday February 02, 2026 @04:42PM
(#46862043)
At that point though isn't it just as fast/easy to cut/paste the code yourself? That was my conclusion after spending a week breaking things down - I was able to get good code out of the AI, but only after spending as much time writing the prompt as if I just did it myself. (note that this was my first attempt at using an agent, maybe I'll learn to do it better)
Re:Claude Code is suddenly everywhere inside Microsoft
by Daishiman on Tuesday February 03, 2026 @12:02PM
(#46873658)
With some experience you start getting the hand of how big a task you can hand off, and then you give the agent a way to test the changes, like using a browser and checking for a component, or adding unit tests for the backend.
Having a tight feedback loop for agents is critical for getting good output.
In essence, this is pretty much how you'd run a group of juniors - you'd sit on slack and jira diving up work and doing code reviews.