70 points by autocode 1 year ago flag hide 18 comments
user1 1 year ago next
Great project! I've been looking for something like this. Can't wait to try it out.
user2 1 year ago prev next
Thanks for sharing! I've been using it for a few days now, and it's been catching issues I didn't even know I had.
user3 1 year ago next
That's so cool to hear! I'm glad it's helping. Have you tried the feature where it also suggests fixes?
user2 1 year ago next
Yes! It's been amazing. It's like having an extra developer on the team who's sole focus is on code quality.
user4 1 year ago prev next
Does it work with language XYZ?
user1 1 year ago next
We do support language XYZ, but it's currently in beta. Let us know if you have any issues with it.
user5 1 year ago prev next
I've been using it for a few days now, and I keep getting a lot of false positives. I'm not sure how to configure it to be more specific.
user1 1 year ago next
I'm sorry to hear that! We're always looking to improve our algorithms to reduce false positives. We have some documentation on configuring the thresholds and sensitivity levels, which you might find helpful.
user6 1 year ago prev next
This is amazing! I'm using it in my team of 10 developers, and it's been saving us so much time and improving our code. Thanks for open sourcing it!
user1 1 year ago next
Thank you so much for letting me know! It's been so rewarding to see people using it and getting value out of it. That's exactly why I decided to open source it.
user7 1 year ago prev next
I have a question about the license. Is it compatible with commercial projects?
user1 1 year ago next
Yes, it is. It's under the MIT license, which allows for commercial use.
user8 1 year ago prev next
Have you considered adding support for static code analysis?
user1 1 year ago next
Yes, we've thought about it, and it's on our roadmap. The challenge is in making the alerts understandable and actionable, especially when there are so many static analysis tools out there, each with its own terminology and level of sensitivity.
user9 1 year ago prev next
Just deployed it in my company of 50 developers, and I'm getting reports that the results are overwhelming and causing a lot of noise. Any suggestions on how to manage it?
user1 1 year ago next
I'm sorry to hear that! It can be overwhelming at first as there might be a lot of issues. I would recommend starting by setting up custom rules and filters to suit your team's needs and addressing high priority issues first. We've also seen people using it in phases, like first running it on a small codebase or for a limited time duration to get a feel for it and build trust within the team before running it on larger projects or making it a regular process.
user10 1 year ago prev next
Thanks for sharing this! I've been struggling with code reviews and couldn't find an efficient way to do it. Gonna give this a try.
user1 1 year ago next
You're welcome! I hope you find it helpful. Let me know if you have any questions or run into any issues.