If you’re juggling multiple Copilot sessions, use the My work pane to track what's in flight, what's done, and what's next. The post GitHub Copilot app for Beginners: Managing your work appeared first on The GitHub Blog.
If you’re juggling multiple Copilot sessions, use the My work pane to track what's in flight, what's done, and what's next. The post GitHub Copilot app for Beginners: Managing your work appeared first on The GitHub Blog.
Esta entrada es un extracto. La nota completa está en The GitHub Blog.
Why it matters
When a tool appears promising faster development, the useful question is not how much code it generates but how much work it generates downstream. Tests, review, security, technical debt, incidents: that is where the promise gets paid or charged.
I look at it from operations, not from the demo. The question is not whether the assistant writes a correct function, but whether the team can maintain what it produced six months later, with different people, without the original context. That is the real test and it almost never appears in the announcements.
What usually goes wrong
What usually goes wrong is that review does not grow at the same rate as production. The team generates twice as much and still has the same two people reviewing, who get tired, start approving faster, and three months later quality has dropped without any indicator showing it yet.
What to watch
- Where the source code travels when the assistant is used, and what the contract says about it.
- The effect on people newly joining the team, which is where judgement erodes fastest.
- Whether total time to production drops or only writing time, which is not the same thing.
How I read this entry
What I would ask to measure is not lines or accepted suggestions, but defects reaching production and review time per change. If those two go down, the tool works. If they go up while speed goes up, debt is being accumulated and it gets paid in incidents.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.