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
Cool, good to hear. I think it’s often the case even within an individual file or change that it’s 90% routine and 10% critical to review. That’s a big part of the problem in my mind.
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 tool can help make that easier
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
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
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 with new security review features that are more suited towards that use case
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!
reply