Show HN: We manage your code duplication. We want your bugs to stay fixed
qamine.com
qamine.com
I heard if you don't repeat yourself then you don't run into this kind of thing, but agile startup nodejs ninjas have no time for that
But seriously, this seems to be checking for the antithesis to good code and I imagine a lot of programmers here are thinking 'you shouldn't need it!'. So sell it a bit more as your website doesn't.
On the code bases you've beta tested this on, do you really identify this kind of percentage of replication? Isn't that a sign the code is bad and should be abstracted or does this help in another way?
I'd want to see some real life examples on your site somewhere on some public repos, where are they!
1) You don't have time to refactor 2) The overhead of refactoring is too big
So for all these cases, we believe you should be able to live with the code you have and not make any inconsistencies.
Showing real life examples is definitely interesting.Will improve.
Thank you for this.
My submission never made it to HN front-page, but I would love any feedback on it. It's at www.bisect.cc. Thanks.
(Jaime, your service is really the kind of functionality that is missing from dev toolbox. Great job at solving real-world problems!)
Bisect allows users to test program state against expected values. Tests results are used as bisection READING STOPS HERE points to narrow-down towards the root-cause of the underlying issue.
The top three paragraphs still don't really explain what this does. Summarize, and show an example. That way, people will use it and come back to it.
Awaiting a Sublime Text plugin or growl integration, as email is not really in my workflow.
Aha, awesome stuff. Thank you for your love. Please let me know if you ever need anything (jaime@qamine.com/jaime.fjorge) If Qamine is essential to you, I would love to give you extra credit/bugs and a hug for that testemonial.
Thank you for sharing the love!
Congratulations!
A few commments:
1) When you first login, I have no idea what to do. When I clicked on my profile, the tour kicked in and was very helpful. Why no tour on the first screen?
2) The red X button for each repository is a little weird. It makes it look like the repository isn't eligible, or there's an error. Probably should do something different there.
3) When I click the red X button it turns blue with a clock icon, and then after some time turns back to the red button again. As a user I have no idea what's happening. As a dev, I can only imagine you're getting pounded and something's failing in the background.
Thanks for the feedback. I'll try to spot your registrations and make them work.
1) When I signed in, there were initially no projects shown. I had to refresh to see anything.
2) When I click to start analysis, the application just loads... for ages and then crashes ('An error occurred in the application and your page could not be served. Please try again in a few moments.') I'm sure that's just teething issues, but it would be nice to have some kind of ajax loading icon to show the application is thinking :-)
Thank you for the time to write that.
Check out CloudFlare - they do a great job with this exact situation in their record import screen.
What we have seen is that startups don't have more than 5-10 clone detection inconsistency issues. So we want basically to provide that value for you for free. And, as soon as you outgrow that number because you have 1) a larger team 2) more code, you will be able to afford the subscription.
Thanks for the feedback!
Thank you for your kind words!
Also, the product tour really isn't very useful at three steps. Seems like a more streamlined 'onboarding' experience is what you are after.
Thanks for the feedback. That's exactly what I'm looking for.
is this a github default? Because I now simply dont know exactly what oAuth I am giving away so I dont want to give it.
help?
I would not give anyone access to all my private repositories, however.
I suspect this isn't a coincidence.
SVN is definitely also on our roadmap. A couple of companies already asked for it. We already have a prototype version of SVN integration running..
Would love to have it running on your clients. Let's talk about it (jaime@qamine.com)
Those tools evidence your code duplication (saying the lines and code regions). We, however, show you when those code regions were changed inconsistently.
We basically want to show you the effects of code duplication by introducing time whereas those tools don't have the concept of time.
If you ran those tools every single time you commit to see if you forgot to change a code region, you don't need us. If you're interested in having that ran for you, that's where we come in.
Thank you for your question. I hope to have answer it?
Because it is growing, however, I can assure you that it will be our next integration :) Sign up (or ping me: jaime@qamine.com) and I'll update you.
Thanks for the interest!