5 ms·

As the founder of a quite similarly named company, this looks great :) Not sure if you're looking for a job Katherine, but if you are my email is in my profile!

parhamn 6y ago
This felt genuine. But I must admit, asking someone launching something if they're looking for a job rubbed me the wrong way. :shrug:
- gkoberger 6y ago
  I would never try to dampen someone's enthusiasm for launching a company! However, based on how she talks about readme.so on Twitter and the fact that it's free and open source, it's clear she built it just to build something cool. If she's open to a job, then she gets to continue working on something called ReadMe that's in a similar vein! If she's not, for whatever reason, then there's no harm done and I hope she takes my comment as a compliment :)
- ZephyrBlu 6y ago
  If I was the person who launched this, being offered a job like this would be really cool even if I didn't take it.
nyellin 6y ago
I love the concept of Readme.io but I chose Sphinx over Readme.io for my startup despite starting out with Readme and really wanting it to work. A few issues: 1. Linking other pages is buggy. Sometimes Readme autocompletes the page name and sometimes it doesn't. In general, the UI feels a little buggy and that's a big issue given that it's the entire reason I'm using your product. 2. I couldn't figure out how to make my docs publically available during the trial. I still don't know if this is because actually making your docs public is a paid feature or if I couldn't find the right button. 3. I desperately needed an export to pdf and that wasn't available during the trial despite the promise on the home page that the trial includes all features. 4. My cofounder thought the price was a little high given how easily we could handle docs ourselves. There were some things I really liked: 1. I love the way you can embed API keys in the docs based on the reader's identify. 2. The API related features also look cool, although they aren't relevant for us. Lastly, I'm not a customer in the end but one feature that I would have paid for (at the time when I was still evaluating this) is the ability to password protect docs and allow access only to specific people you invite. (Not paid users on your own team though. Just people you invite as readers.) We're still mostly in stealth mode but we do have prospects trying out our software regularly and would like to send them a nonpublic version of the docs that they can see. (Hence my desire to export to pdf, but private docs would be better than pdf.)

parhamn 6y ago

This felt genuine. But I must admit, asking someone launching something if they're looking for a job rubbed me the wrong way. :shrug:

gkoberger 6y ago
I would never try to dampen someone's enthusiasm for launching a company! However, based on how she talks about readme.so on Twitter and the fact that it's free and open source, it's clear she built it just to build something cool. If she's open to a job, then she gets to continue working on something called ReadMe that's in a similar vein! If she's not, for whatever reason, then there's no harm done and I hope she takes my comment as a compliment :)
ZephyrBlu 6y ago
If I was the person who launched this, being offered a job like this would be really cool even if I didn't take it.

nyellin 6y ago

I love the concept of Readme.io but I chose Sphinx over Readme.io for my startup despite starting out with Readme and really wanting it to work. A few issues: 1. Linking other pages is buggy. Sometimes Readme autocompletes the page name and sometimes it doesn't. In general, the UI feels a little buggy and that's a big issue given that it's the entire reason I'm using your product. 2. I couldn't figure out how to make my docs publically available during the trial. I still don't know if this is because actually making your docs public is a paid feature or if I couldn't find the right button. 3. I desperately needed an export to pdf and that wasn't available during the trial despite the promise on the home page that the trial includes all features. 4. My cofounder thought the price was a little high given how easily we could handle docs ourselves. There were some things I really liked: 1. I love the way you can embed API keys in the docs based on the reader's identify. 2. The API related features also look cool, although they aren't relevant for us. Lastly, I'm not a customer in the end but one feature that I would have paid for (at the time when I was still evaluating this) is the ability to password protect docs and allow access only to specific people you invite. (Not paid users on your own team though. Just people you invite as readers.) We're still mostly in stealth mode but we do have prospects trying out our software regularly and would like to send them a nonpublic version of the docs that they can see. (Hence my desire to export to pdf, but private docs would be better than pdf.)