codeapprove

6 ms·

31.
by codeapprove 3y ago
Shameless plug but if you dislike GitHub's code review UI you could try my product, CodeApprove ( https://codeapprove.com ). There are actually dozens of great code review tools out there: https://medium.com/c
32.
by codeapprove 3y ago
I generally think of code review like static typing: many people think they don't need it but pretty much every serious large codebase uses it and needs it. And just like coding with types: code review does not have to be a chore! With
33.
by codeapprove 3y ago
Oh wow something must have been in the air! I have been working on a very similar project lately, I think a lot of companies need this and your feature set looks great. So it's safe to say I think this is a great idea and I wish you su
34.
by codeapprove 3y ago
I’m obviously biased but you might like https://codeapprove.com , it’s a GitHub-compatible code review UI for power users. There are actually a lot of good options in the space these days (Reviewable, Graphite, etc) so there’s no
35.
by codeapprove 3y ago
Even at Google, most people find Gerrit to be pretty intimidating. It’s mostly only used for Chrome, Go, and Android and it’s far behind Google’s flagship review tool (Critique). Gerrit is not a bad tool but it is somewhat hard to get used
36.
by codeapprove 3y ago
GitHub definitely does support (1)! You just comment and click “add to review” as you go and then submit them all together at the end. It’s been the default for a while now. For (2) you definitely want Gerrit. For major improvements on (1),
37.
by codeapprove 3y ago
Wow this looks great. I really like the additions of presence and the stats about review times. It seems seamlessly integrated. As you might be able to tell from my username, I’m the founder of CodeApprove (codeapprove.com) which is meant t
38.
by codeapprove 3y ago
Looking good Fahrzin! It's a nice update on the landing page without a total overhaul of the Reviewable look/brand.
39.
by codeapprove 3y ago
I was actually in charge of a large open-source effort at Google (75 repositories, dozens of internal devs, hundreds of contributors) so I had a very unique position of being able to watch Googlers attempt to use Google engineering practice
40.
by codeapprove 3y ago
There are a lot of great tools in the space right now, I firmly believe that teams should not just accept what GitHub gives them. After all, we don't use Notepad as our main editor just because it ships with the machine. I started Code
41.
by codeapprove 3y ago
Looks really nice! Also I love the level of personality on the marketing page, it's nice to see a product not taking itself too seriously. Just curious, this seems to have a lot of overlap with Axolo ( https://axolo.co/
42.
by codeapprove 3y ago
All great points, and I appreciate them because I think CodeApprove's marketing materials should address them more head on. The first two (trust with repos and GitHub API rate limits) don't really apply to CodeApprove in the same
43.
by codeapprove 3y ago
(shameless plug alert) If you're looking for a drop-in improvement to GitHub's code review experience, you may be interested in CodeApprove ( https://codeapprove.com ). It's got a lot of the things that make Gerrit
44.
by codeapprove 4y ago
Wow this looks really nice! The AI-grouped (and described) file changes is something I have never seen before, and I thought I'd seen everything in code review. A lot of what you're doing is similar to what I've been trying t
45.
by codeapprove 4y ago
CodeApprove: https://codeapprove.com Basically CodeApprove is a code review UI for power users to layer on top of GitHub. I find that it really resonates with people who have worked at Google/Facebook/etc before and fi
46.
by codeapprove 4y ago
I am biased here since I am the creator of an async code review tool (codeapprove.com) but I think that many teams don't take the time to invest in their code review process and tools enough. For something that most of us do every day
47.
by codeapprove 4y ago
I agree that the tooling is very underrated! It’s strange that programmers spend so much effort choosing their code writing environment (IDE, etc) but just take what they’re given when it comes to code reviewing (mostly GitHub PRs) If you’r
48.
by codeapprove 4y ago
As someone who is a big proponent of "squash and merge" I am susprised to see myself labeled an extreme clean freak! I don't have very extreme git uses or opinions. I want a few things in my team's workflow: * A commit h
49.
by codeapprove 4y ago
Thanks for the link to Basecamp's policies! I think that's exactly what I was looking for.
50.
by codeapprove 4y ago
Thanks fir the link to Termsfeed! At least it has one-time pricing and self-hosting, that's great. Termly in particular seems to go out of their way to present the terms as an HTML/CSS/JS combination that is surprisingly hard
51.
Ask HN: How do you write a “Terms of Service” for your startup?
16 points by codeapprove 4y ago|14 comments
52.
by codeapprove 4y ago
Interesting stuff! I feel somewhat validated to see that there's not an empirical relationship between change size and time to merge because I've always disliked the "small PRs police". I'd personally argue that the
53.
by codeapprove 4y ago
That’s what we’re trying to do at CodeApprove: build a code review tool for power users. UX is a huge part of it. If you’re interested, check out https://codeapprove.com
54.
by codeapprove 4y ago
Shameless plug but at CodeApprove we’re pretty obsessive about giving the GitHub PR review experience “more love”. Check out https://codeapprove.com if you’re interested
55.
by codeapprove 4y ago
The key to these types of interactions is to make them impersonal. In the case of coding standards (which don't have to do with logic/implementation) try to get all of them enforced by either an automated linter/formatter or
56.
Modern code review tools (2022)(medium.com)
8 points by codeapprove 4y ago|2 comments
57.
by codeapprove 4y ago
CodeApprove founder here! If you want to chat, my email is in my HN profile.
58.
by codeapprove 4y ago
One obvious benefit of the internal tools at Google is that they're all integrated with each other. So any Googler can quickly: 1. Search another team's code 2. Quickly jump into a Cloud IDE to make a change 3. Build and test the
59.
by codeapprove 4y ago
Graphite is excellent! Shameless plug but anyone interested in a code review tool on top of GitHub may also want to check out CodeApprove ( https://codeapprove.com ). It's got a lot of the things that people from FAANG compan
60.
by codeapprove 5y ago
Everything in the article rings true. We as authors/reviewers can do a lot more to prove that the code works and much of that doesn't actually involve reading diffs. However I think people often underrate how bad their basic code

More ›