Live data from Hacker News

Show HN: Slack Meets GitHub Issues

news.ycombinator.com

71–80 of 164 posts

Re: Show HN: Slack Meets GitHub Issues

#71

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…

Hi there, your assessment is very critical and I was wondering whether you would so kind as to assess a project I am working on. www.cograph.co Thank you!

Re: Show HN: Slack Meets GitHub Issues

#72

Can someone explain to me the apparently common obsession with creating to-do lists and chat programs? I can't figure out why so many people devote this much of their time to building to-do lists.

Developers tend to have a lot of activities and tasks they need to keep track of, and it's too much to remember. So we all wind up making lists: on paper, on whiteboards, in text files, in email, in apps. These lists always start out being fairly simple and manageable, but they also always grow into an unmanageable mess.

Being developers, we wind up blaming the record-keeping tool for the unmanageable mess rather than our own habits. That leads us to think that if we could just create a better tool for keeping track of our TODO list, our lives would be easier to manage, and maybe others could benefit from the tool as well.

Of course it never seems to pan out, because what we're trying to manage is our (work) lives, and our lives cannot be represented as a simple task list. There's a lot more nuance and complexity to it. And that's why we end up with a million different implementations of simple TODO lists.

Re: Show HN: Slack Meets GitHub Issues

#73
You might have a hidden diamond for team collaboration here, but after reading more than most potential customers will, I'm not sure exactly what it is.

I'm not a fan of the to-do/chat combination. There just isn't a lot of intersection between the things on my to-do list and the things I want to chat about. Who wants to chat about their grocery list? Who would contact their family about dinner plans with this instead of a phone call, text message, Tweet, etc. just because they can easily save a to-do item? Perhaps this has other uses.

Consider extremely detailed user stories. Who might want to this? A software product manager communicating with the technical team about features and bugs; a high-school student and her study group; an extended family planning a vacation together?

What would they share, and how does this tool help? Why would they use something new instead of a phone, e-mail, Twitter, Facebook, preferred existing group to-do list app, or a thousand other tools? What are their favorite colors; favorite words; turn-offs?

Kudos on what you've done so far. And remember, even if this fails as a startup (most do), it certainly demonstrates your skills. Hopefully it will open doors.

Oh...and don't bankrupt yourself working on this. That would just be crazy.

Re: Show HN: Slack Meets GitHub Issues

#74
post #42

Earlier quoted context omitted.

I really like the concept and a bunch of the features but echo other thoughts. Also, plzplzplzzplz don't keep something a bunch of people have said they dislike because it came about years ago and you're attached to it.

I agree. "OpenLoop" and "OpenLoopz" is enough to justify it.

I was speaking broadly and not actually directly about the name but using the name as an example. :)

Re: Show HN: Slack Meets GitHub Issues

#75
post #49
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…

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!"

Re: Show HN: Slack Meets GitHub Issues

#76
post #66

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…

#middlebrow_dismissal

Please don't mistake harsh but constructive criticism for middlebrow dismissal.

Re: Show HN: Slack Meets GitHub Issues

#77
You need to adjust the content on the first page of the site to match some things from the blog post, describing what it is. It would be great if you could add screenshots / gifs so people can quickly understands what it is.

There are too many apps created that say nothing on their landing page, and it feels frustrating for users when they cannot find / understand "what is this?".

Best of luck!

Re: Show HN: Slack Meets GitHub Issues

#78

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.

Re: Show HN: Slack Meets GitHub Issues

#79
post #74

Earlier quoted context omitted.

I agree. "OpenLoop" and "OpenLoopz" is enough to justify it.

I was speaking broadly and not actually directly about the name but using the name as an example. :)

Ok. I still think my view is valid in terms of what people are trying to say. But yeah, what's best for business > being overly attached to something.

Re: Show HN: Slack Meets GitHub Issues

#80
post #25

Earlier quoted context omitted.

I hope whenever I submit something to HN that 1) someone cares enough to be this critical\constructive and 2) I am adult enough not to take it on the chin and not get sulky. I'm most worried about #2

I am the OP and I would hate it if I had a few "this is cool" comments and no constructive criticism. I really appreciate it. When I first read some of the harsher feedback on here, it did feel like a punch in the face - I won't lie ;-) But then I took a deep breath and read it again objectively and actually tried to take it in. And 99% of what's here is excellent feedback. I wasn't expecting any responses, honestly…

I'm not in a position to critique the product at the moment, but it looks like there's plenty of feedback for you to work through anyway. Good luck!
Post reply on HN