Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Slack Meets GitHub Issues

news.ycombinator.com

Post reply on HN
Print view View original

121–130 of 164 posts

Re: Show HN: Slack Meets GitHub Issues

#121

Post by igorgue »

weego wrote: post #115
nkohari wrote: post #89

Earlier quoted context omitted.

You spent 15 minutes looking at the beta version of a product, and you've made the decision that the creator is wasting their time? Have you considered that, having thought about it for months, they might understand the problem domain significantly better than you? What if the product actually has tremendous value, but suffers from a marketing problem? That's a pretty easy problem to fix. Rather than using your sever…

I don't know whether you really are just hedging your bets to karma farm or whether you believe what you say but the author has stood up and asked what people think. What on earth is the point of everyone on here going "oh well it's not up to us to say what we think; he should just start stacking up debt on credit cards and bank loans until it's finished and then the market can dictate!" That is the logical conclusio…

How was traffic today?

Re: Show HN: Slack Meets GitHub Issues

#122

Post by nkohari »

weego wrote: post #115
nkohari wrote: post #89

Earlier quoted context omitted.

You spent 15 minutes looking at the beta version of a product, and you've made the decision that the creator is wasting their time? Have you considered that, having thought about it for months, they might understand the problem domain significantly better than you? What if the product actually has tremendous value, but suffers from a marketing problem? That's a pretty easy problem to fix. Rather than using your sever…

I don't know whether you really are just hedging your bets to karma farm or whether you believe what you say but the author has stood up and asked what people think. What on earth is the point of everyone on here going "oh well it's not up to us to say what we think; he should just start stacking up debt on credit cards and bank loans until it's finished and then the market can dictate!" That is the logical conclusio…

1. I don't comment often, and when I do, it's not to earn magical internet points.

2. I am certainly not advocating diffuse positivity. If you knew me, you would know positivity is not my strong suit. :)

There's nothing wrong with saying that the product seems unfocused or overly complex, or suggesting that the creator focuses either the execution or its messaging. That's useful, constructive feedback that the creator can do something with.

There's not really even anything wrong with saying "I don't understand why anyone would use this" -- although that's not particularly useful feedback.

Jumping from these reasonable positions to "you're wasting your time" is where I take issue. It's a dangerous leap of judgement that none of us can or should make for someone else -- certainly with the limited understanding that we can gain after a few minutes.

The creator seems to have come here to get feedback on the product, not for an intervention.

Re: Show HN: Slack Meets GitHub Issues

#124

Post by ericfontaine »

"Open" to me leads me to think it is open source, but it isn't. I suppose common folk may not have that presumption. But I don't even think "Open" is descriptive to what your product does (other than maybe how it is quick to open). Loop is fine, as it express to me how you can be "in the loop". If you are getting rid of the Z or thinking of other names, I suggest using parts of another commentor's suggested tagline: "chat is your to-do list, and your to-list is your chat" for the name: e.g. "ChatToDo", "TagToDo", "LoopToDo", "TagChatDo", or even simply "InTheLoop" is better. Something along those lines that is more direct, specific, & descriptive than OpenLoopz, so that an uninitiated potential consumer has a bit of an idea about what it is your app does before even considering to click your link.

(Regarding the www., I was another of those who just visited the naked url, and I immediately thought negative thoughts like, it's down, and almost didn't try again. You should atleast redirect the naked url to a valid url or landing page.)

Re: Show HN: Slack Meets GitHub Issues

#125

Post by thebouv »

api wrote: post #120
nkohari wrote: post #89

Earlier quoted context omitted.

You spent 15 minutes looking at the beta version of a product, and you've made the decision that the creator is wasting their time? Have you considered that, having thought about it for months, they might understand the problem domain significantly better than you? What if the product actually has tremendous value, but suffers from a marketing problem? That's a pretty easy problem to fix. Rather than using your sever…

If I had a dolla' for every similar throwaway comment about my own project, I would not need any funding. Hey, maybe this can be a new startup funding mechanism. I propose "haterade.io", a betting pool where you can bet that projects will fail by a certain time. If you lose, your bet goes to the project. Edit: the real problem is the OP's tone . I do agree that the founder of this project has an explanation problem,…

My first bet is that haterade.io will succeed. Insert cash where?

Re: Show HN: Slack Meets GitHub Issues

#126

Post by thebouv »

onion2k wrote: post #81
mdemare wrote: post #75

Earlier quoted context omitted.

Also, people who can't pronounce voiced consonants at the end of syllables (such as german, dutch, french people) can't help but hear it as FuckBugs. "Ve still neet a buck trecker, I vas finking about Jira, or do you haef a better idea?" "Yes, I recommend FuckBugs!"

To be fair though, FuckBugs would be a brilliant name for a bug tracker.

Let's build it.

In BrainFuck.

Re: Show HN: Slack Meets GitHub Issues

#127

Post by zackliscio »

leftnode wrote: post #28

I'll come out with a contrarian point of view: I think you're wasting your time and certainly your money. To have invested your life savings into this app which, uh, is really hard to determine what it does seems silly to me - especially since you have a family to care for. Slack Meets GitHub Issues? Doesn't Slack already meet GitHub issues in that it integrates with GitHub fine? The fact that you need a very long bl…

For what it's worth, releasing something and finding little or no adoption of the product is often where the interesting learning begins.

I can't tell you whether or not it's worth pursuing, but I know that in my own experience it was. Our team spent almost a year building and launching a product that we ultimately shut down. We could have stopped and gone back to our day jobs, but the silver lining is that the core technology became the foundation for our current (seemingly unrelated) company.

While the now-forgotten product we launched was a failure, pushing past that resulted in a product that has been far more successful (funding, product-market fit, etc). There's no guarantee you'll pivot into success, but there's zero chance you will succeed if you stop iterating.

Re: Show HN: Slack Meets GitHub Issues

#128

Post by varunjuice »

Lewisham wrote: post #90
varunjuice wrote: post #69

Earlier quoted context omitted.

Right on. Somebody should've told Mark about the saturated social media market, or Larry about the saturated search market. There are so many communication tools, surely its a solved problem right. Ask a knowledge worker today about their favorite communication tool, and you will end up with a dozen answers in about a week's time. Definitely a sign that the problem is solved. There are a dozen solutions after all. :)

This is needlessly reductive and misses the point: the issue isn't saturation, the issue is that OP hasn't identified the USP of the product. Zuck knew full well that the USP of The Facebook was helping students get laid (or at least, find out more about that pretty boy/girl in your class). Larry knew full well that the USP of Google was that PageRank helped identify better quality web sites. OP doesn't really know w…

I'm latching, probably unfairly, to the comment about "market saturation". I give OP +1 for conviction, and -1 for lack of validation.

Re: Show HN: Slack Meets GitHub Issues

#129

Post by thebouv »

Some of this you've already heard in other posts, but since I'm figure you're hungrily looking at all these posts to help yourself out, I'll give some bulleted advice at the risk of repeating:

1) Get an editor. You may be a great coder, but you're not the best copywriter. Neither am I. So I don't write my own product copy. It will do wonders for your product's image.

2) Video / screencast / visually show me the product without having to sign up for Beta. I'm busy and words take too long to read.

3) This might be nit-picky, but the name really puts me off. It's the Z, man, it hurts.

4) Does your software solve a problem? If so, can you explain the problem to me in two sentences? I still don't understand as I don't use Slack, even though I know what it is.

Best of luck to you. I hope to hear about your acqui-hire or buyout soon enough.

Re: Show HN: Slack Meets GitHub Issues

#130

Post by api »

thebouv wrote: post #125
api wrote: post #120

Earlier quoted context omitted.

If I had a dolla' for every similar throwaway comment about my own project, I would not need any funding. Hey, maybe this can be a new startup funding mechanism. I propose "haterade.io", a betting pool where you can bet that projects will fail by a certain time. If you lose, your bet goes to the project. Edit: the real problem is the OP's tone . I do agree that the founder of this project has an explanation problem,…

My first bet is that haterade.io will succeed. Insert cash where?

I'm too busy to disrupt the hater market. Anyone else is free to take that idea.
Post reply on HN