- Time to build an aggregator for Claude Code enabled teams that just generates the unimportant updates of Stand-ups into pre-reads, so the team can cut to blockers/important shit?
- Do you think there's a way to analyze productivity with this data?
I think there is really good potential for that. ~/.claude is an quite the audit trail, if i look at the react app scaffold i built you can really see the story of that dev's day.
This is under the premise that the devs in questions are "agent first" in their work with Claude Code. Claude only has perspective on what it was asked to take on. If you have a dev that uses Claude for "light advisement" only, these audit trails will just not have the complete perspective.
For myself being in the Research/Experiment realm, I use CC for really everything, it has perspective on ideation, planning, and implementation, I truly "pair" with Claude for my work.
Two thoughts:
- Time to build an aggregator for Claude Code enabled teams that just generates the unimportant updates of Stand-ups into pre-reads, so the team can cut to blockers/important shit?
- Do you think there's a way to analyze productivity with this data?
I think there is really good potential for that. ~/.claude is an quite the audit trail, if i look at the react app scaffold i built you can really see the story of that dev's day.
This is under the premise that the devs in questions are "agent first" in their work with Claude Code. Claude only has perspective on what it was asked to take on. If you have a dev that uses Claude for "light advisement" only, these audit trails will just not have the complete perspective.
For myself being in the Research/Experiment realm, I use CC for really everything, it has perspective on ideation, planning, and implementation, I truly "pair" with Claude for my work.