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

81–90 of 164 posts

Re: Show HN: Slack Meets GitHub Issues

#81

Post by onion2k »

mdemare wrote: post #75
onion2k wrote: post #49

Earlier quoted context omitted.

If you're Joel Spolsky you can release a piece of software with any name you care to choose and people will still take it seriously because you have earned the respect of your peers. Other people who don't have decades of experience producing exceptional software don't have the same luxury. Fogbugz is a terrible name and if an unknown developer had released it there's a good chance too few people would have looked at…

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.

Re: Show HN: Slack Meets GitHub Issues

#82

Post by rmc »

onion2k wrote: post #49
switz wrote: post #43

Earlier quoted context omitted.

While the name is not perfect, I don't believe it is as dramatic as you are making it out to be http://www.fogcreek.com/fogbugz

If you're Joel Spolsky you can release a piece of software with any name you care to choose and people will still take it seriously because you have earned the respect of your peers. Other people who don't have decades of experience producing exceptional software don't have the same luxury. Fogbugz is a terrible name and if an unknown developer had released it there's a good chance too few people would have looked at…

FogBugz was released in Nov 2000. How big was Joel Spolsky then? (It's before my time.) It looks like Joel was hardly blogging when FogBugz was released ( http://joelonsoftware.com/backIssues.html )

Re: Show HN: Slack Meets GitHub Issues

#84

Post by minimaxir »

leereeves wrote: post #78
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…

I agree, and disagree. What this product would be useful for isn't explained well, and I'm not sure even the OP knows. But there's clearly something compelling here based on the attention we've all given it.

> But there's clearly something compelling here based on the attention we've all given it.

It should be noted that the original title contained an "I quit my job" affectation, which may have biased the original upvotes for the submission. (which is why the affectation was removed)

If the submission was simply a link to the service instead of a story, I would imagine the results would be much different.

Re: Show HN: Slack Meets GitHub Issues

#88

Post by austenallred »

leereeves wrote: post #78
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…

I agree, and disagree. What this product would be useful for isn't explained well, and I'm not sure even the OP knows. But there's clearly something compelling here based on the attention we've all given it.

I'm not sure that conclusion necessarily follows here. This wasn't just a link to a product, but a story, starting with, "I quit my job and sacrificed a lot to get here."

Something being is interesting or worth talking about doesn't necessarily mean that thing is valuable (or a good idea for a company). An upvote doesn't necessarily mean, "I like this," but rather, "this is interesting" (or whatever other metric one uses when determining whether to upvote).

I upvoted the OP because I thought it was interesting that someone had quit their job and sacrificed so much to work on something. I didn't look farther than the Medium post because I feel like Slack already has this angle covered.

Or it could be that I'm just not the right audience or I don't get it.

Re: Show HN: Slack Meets GitHub Issues

#89

Post by nkohari »

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…

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 severely limited understanding to encourage the creator to throw the baby out with the bathwater, you should focus on tangible, solvable problems, or just keep your mouth shut.

Re: Show HN: Slack Meets GitHub Issues

#90

Post by Lewisham »

varunjuice wrote: post #69
mydpy wrote: post #60

Earlier quoted context omitted.

I agree with your assessment. I don't think this product has the type of competitive advantage needed in this highly saturated communications market. I think you can use this to lead to better things. Iterate on the product, get some feedback, and attack it again. In the meantime, blog throughout the process. Get your voice out. If you generate interest about your product before you release it, you can generate more…

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 what the product is himself, so cannot begin to differentiate.

Post reply on HN