cpan22

6 ms·

1.
by cpan22 4mo ago
I switched over to Superset from Conductor a few months ago and haven't looked back - it's really nice to be able to use the native Codex/Claude Code TUIs without any of the bloat Can't wait to see what else you guys coo
2.
by cpan22 4mo ago
+1, git diffs show you the changes in repository list order but sometimes it makes more sense to read certain things first - our tool does just that
3.
by cpan22 4mo ago
Nope! this is completely free :)
4.
by cpan22 4mo ago
yes! we've found that reading changes this way make it very easy to separate the important stuff from the unimportant stuff, and we're thinking of ways to make that more visible in the UI
5.
by cpan22 4mo ago
yep sorry about that, we weren't exactly sure what the best framing was glad you like the idea though! let us know what you think
6.
by cpan22 4mo ago
we're planning on adding it!
7.
by cpan22 4mo ago
Great let us know what you think! And yeah, I think number 5 on your list is particularly interesting - juniors will develop much slower if they don't go through the struggle of understanding implementation We're hoping that our t
8.
Show HN: Stage CLI – An easier way of reading your AI generated changes locally(github.com)
46 points by cpan22 4mo ago|32 comments
9.
by cpan22 5mo ago
Well I think the bigger issue here is that GitHub is too decoupled from an issue tracking system - its a lot of manual overhead to constantly have to keep in sync. Linear does an ok job but far from ideal
10.
Introducing Stage: Engineers deserve a better code review platform(stagereview.app)
3 points by cpan22 5mo ago|1 comments
11.
by cpan22 5mo ago
Yeah we've been thinking a lot about this! Switching back and forth between local and GitHub is also a frustration of ours so we want to think of ways to unify the experience
12.
by cpan22 5mo ago
Good question, we're more focused on the first aspect you mentioned of "does the code you wrote make sense on a high level" rather than "did you miss something" - I think tools like Greptile and Codex are coming out
13.
by cpan22 5mo ago
Great point and that's our takeaway too from talking to many users. We're exploring ways for Stage to possibly tailor the review flow to each specific PR/user preferences. Would love to hear any ideas if you have any!
14.
by cpan22 5mo ago
Yep that seems to be a common sentiment! Definitely some interesting areas around capturing agent conversations in commit history that could make this possible
15.
by cpan22 5mo ago
Good point, we've heard from users that there's a lot of fatigue of switching between local and GitHub all the time so we're thinking of ways to unify that experience
16.
by cpan22 5mo ago
Agreed! That's why we designed Stage with the intention of AI guiding the human, not replacing them
17.
by cpan22 5mo ago
Thanks for sharing this, I do agree with a lot of what you said especially around trust around what its actually telling you For me, I only run into problems of an agent misleading/lying to me when working on a large feature, where the
18.
by cpan22 5mo ago
I agree with that - with Stage we're not trying to replace reading code with AI summaries, but rather guiding the reviewer through reading code in the way that makes most sense and coming away with the best understanding
19.
by cpan22 5mo ago
Sorry to hear that! Looking into it
20.
by cpan22 5mo ago
Totally fair, we're working on it!
21.
by cpan22 5mo ago
Totally get that, still something we're actively talking about! Sort of related to that, we've been thinking a lot about the future of code review for OSS. Its clear with Cal.com going closed source that something needs to change.
22.
by cpan22 5mo ago
Yep! Or Linear, etc Or could be something like git-ai which captures agent context in git commits
23.
by cpan22 5mo ago
Yep, for me personally, code review was the most effective way for me to get up to speed when joining a new engineering team
24.
by cpan22 5mo ago
Yeah this is a really interesting perspective! We've wondered about what the review experience should look like for newly technical or non-technical people now that they are increasingly putting up PRs themselves. These people will be
25.
by cpan22 5mo ago
No worries at all, that's a very fair point and a question we've gotten a lot! I think our perspective is that: software design has always had a subjective element to it. There's never been a "right" way to design a
26.
by cpan22 5mo ago
I agree, and that's why we're not building a code review bot which aims to take humans out of the loop We don't think of Stage as moving people further away from code review, but rather using AI to guide human attention throu
27.
by cpan22 5mo ago
Thanks for the feedback! re: local vs cloud, I do think there is a cool work to be done around unifying the writing/reviewing experience locally, but we started with cloud because we designed this as a collaborative product with teams
28.
by cpan22 5mo ago
Yep that's something we're actively working on! would love to hear any perspectives on best ways to approach this
29.
by cpan22 5mo ago
Nice! Will try it out
30.
by cpan22 5mo ago
Thank you! Let us know any ways we can make it better

More ›