Show HN: My public YC application, open to any feedback

#1

Post by dreamux » Mon, Oct 10, 2011, 4:52 PM UTC

Show HN: My public YC application, open to any feedback
founderfeedback.com

Re: Show HN: My public YC application, open to any feedback

#2

Post by dreamux » Mon, Oct 10, 2011, 4:55 PM UTC

I've been refining this application for the past few weeks -- but I'm always looking for any feedback I can get. Let me know if you think I should make any last-minute changes (or even what you liked/disliked about it).

Just a reminder that applications are due in tonight. Good luck to everyone!

Re: Show HN: My public YC application, open to any feedback

#3

Post by revorad » Mon, Oct 10, 2011, 5:01 PM UTC

Have you read this? - http://ycombinator.com/howtoapply.html

You seem to fail the PG test for "What is your company going to make?".

"A suite of tools that make software development and team workflows more efficient."

One test of whether you're explaining your idea effectively is to ask how close the reader is to reproducing it. After reading that sentence I'm no closer than I was before, so its content is effectively zero.

Re: Show HN: My public YC application, open to any feedback

#4

Post by dreamux » Mon, Oct 10, 2011, 5:09 PM UTC

revorad wrote: post #3

Have you read this? - http://ycombinator.com/howtoapply.html You seem to fail the PG test for "What is your company going to make?". "A suite of tools that make software development and team workflows more efficient." One test of whether you're explaining your idea effectively is to ask how close the reader is to reproducing it. After reading that sentence I'm no closer than I was before, so its content is effectivel…

The tricky thing is that project management is a very mature industry, so saying that I'm going to build a badass PM tool says even less -- my thought was to focus on the reason for building the tool. My take is that project management in the software space fails because the stacks of tools companies use are rarely interoperable. Efficiency and predictability are hugely dependent on a tight coupling between the different phases of software dev -- and that's where there's still huge amounts of room to innovate.

I hear what you're saying, I just don't know how to rephrase that question to focus on what's innovative...

edit: just to be clear, I think you're right. I'm going to takle this this all day to try to make it clearer. Thanks.