Live data from Hacker News

Show HN: GigaDiff – derisk your release with automated bug prediction

gigadiff.com

1–10 of 22 posts

Re: Show HN: GigaDiff – derisk your release with automated bug prediction

#2
Hey HN,

Happy New year!

I hope to help some companies achieve a more stable environment this year.

Bugs and "tech debt" unfortunately take up the majority of development time where I work. So I wrote something to make it easy to identify problematic functions, giving developers the context they need to make intelligent decisions about when and how to change certain lines of code.

I'd love to get any feedback I can.

Thanks!

Re: Show HN: GigaDiff – derisk your release with automated bug prediction

#3

Hey HN, Happy New year! I hope to help some companies achieve a more stable environment this year. Bugs and "tech debt" unfortunately take up the majority of development time where I work. So I wrote something to make it easy to identify problematic functions, giving developers the context they need to make intelligent decisions about when and how to change certain lines of code. I'd love to get any feedback I can. T…

Congrats on launching!

Why isn't the pricing non-public? Is it customized for each client / use-case? If yes, can you please brief what factors made it infeasible for making it non-public?

Re: Show HN: GigaDiff – derisk your release with automated bug prediction

#5

Hey HN, Happy New year! I hope to help some companies achieve a more stable environment this year. Bugs and "tech debt" unfortunately take up the majority of development time where I work. So I wrote something to make it easy to identify problematic functions, giving developers the context they need to make intelligent decisions about when and how to change certain lines of code. I'd love to get any feedback I can. T…

Congrats on launching! Why isn't the pricing non-public? Is it customized for each client / use-case? If yes, can you please brief what factors made it infeasible for making it non-public?

Hey dotmanish, in short, there's some research I want to do and people I want to consult before making that public. If you're interested, you can email at yahn007 at gmail dot com and we can chat.

Re: Show HN: GigaDiff – derisk your release with automated bug prediction

#6
post #4

huh, Gigadiff strikes me as a terrible name, because it's actively misleading. Without reading the description, I'd think it's about diff that can run on really big files.

Hey pronoiac,

Appreciate the feedback.

To give some context: GigaDiff started as an improvement on "diff" -- almost a diff++ -- in that it would show users which lines changing are associated with bugs in JIRA and occur in stack traces, have been marked as technical debt, or violate linting issues.

But the reason I got all that data together was to use it as signals for ML to detect bugs.

A rebrand in the future is possible. I'm not even sure where I'm going with this project just yet.

Thanks!

Re: Show HN: GigaDiff – derisk your release with automated bug prediction

#7

Hey HN, Happy New year! I hope to help some companies achieve a more stable environment this year. Bugs and "tech debt" unfortunately take up the majority of development time where I work. So I wrote something to make it easy to identify problematic functions, giving developers the context they need to make intelligent decisions about when and how to change certain lines of code. I'd love to get any feedback I can. T…

It sounds like it creates a mapping from lines to "bugginess." How much value do you think there would be in some sort of semantic analysis, e.g. "new function foo is suspect bc it calls bar, which has shown up in a lot of stack traces lately"?

Re: Show HN: GigaDiff – derisk your release with automated bug prediction

#8
Congratulations on launching! This looks like an interesting project.

Your website copy could use some spellchecking – here are some typos I noticed on https://gigadiff.com/features :

  * probility -> probability
  * chnage -> change
  * developes -> developers
  * liklihood -> likelihood
Good luck!
Post reply on HN