I don't think it's a terribly bad idea. As someone said above, doing at least some of the technical legwork yourself will buy you a ton of credibility with experienced programmers when you go to hire. It often becomes somewhat insulting to developers when he/she has to argue schedule with someone with no experience. Often the client thinks it should X should take Y long, and you're telling them that X might not even be possible, but you can do X' in 4 or 10 Y. "What do you mean? You must not be as skilled as so-and-so said you are."

However if you've fought even the initial stages of the battle yourself, you understand the idea of the vision, and the reduced scope which is your next step toward the larger goal. Further, we understand that the part of the learning curve you're in right now is the steepest, and if you're willing to endure it you're either stupid or you really do believe in your business.

> you're either stupid or you really do believe in your business.

haha, I'll refrain from trying to answer that for now ;) You're right in that by far the most challenging part of the learning so far was the first day, and trying to get rails working on a Windows PC. For a person with no technical background, it takes a huge amount of persistence or stupidity to get past that stage.

I actually learned to program so that I'd be in the position to build my own MVCs. The idea came to me as I was learning.

I don't have a lot of money, so I figured the only way to win over a good developer was with credibility (an actual product that at least somewhat works and has some traction).

I appreciate that resources are always tight in these situations so I would recommend that you hire an experienced developer to review your code. It's cheaper than hiring someone full time and you should still be able to get a lot of value out of it. They will know about nuances and gotchas that only years of working on code can teach. Addressing those early rather than late is probably a good idea.

A cheaper (no money but more time spent) alternative is to use forums and IRC channels to get advice. There are plenty of knowledgable people who are more than willing to help if you ask.

Some basics which are vitally important to cover are ensuring that the object model and database schema are solid and extensible, that there are automated tests in place (especially for business critical functionality), that everything is documented (otherwise you will waste inordinate amounts of time explaining how things work to any developers you hire in the future and/or relearning parts of your own code after forgetting what it does) and that everything is backed up to multiple locations. Addressing those concerns puts you well ahead of the pack.

Thanks. Really appreciate the feedback.

It's so tempting to keep build quick and sloppy, but I know I need to be more diligent with testing and documenting.

I'm setting a relatively low target number of users to acquire just to make sure this idea has a chance, before bringing on a developer.

Very broad question, but how does one find an experienced developer? I live in New York, but have zero tech connections.

> It's so tempting to keep build quick and sloppy

That's normal when you're starting out. The only reason more experienced developers do not give into this impulse is because they've learned of the consequences through painful experience.

I would recommend looking at the people who contribute to Rails, Ruby and related projects on Github. The core developers will be far too expensive but people who throw some code out every so often (assuming that their pull requests are usually accepted and nobody is shouting at them in the comments) will likely know their stuff and may have reasonable prices.

IRC channels on Freenode such as #ruby and #rubyonrails will likely prove useful too. Look out for people who answer a lot of questions (and get them right). One strategy is to try to design a solution for a feature by yourself, then summarise the design (i.e. show the relevant code snippets) in a Github Gist or pastebin page and ask for feedback. If there are any glaring faults or simply better ways to achieve the result then they will be pointed out to you.

Thanks for the info. Very helpful. Will check out those sources!

Re: where to find experienced developers with no tech connections, that's not really a problem. Here's why: It's similar to a man asking, "Hey, know any models I can date?"

Actually, beautiful women are hardly rare. But it's the qualifier that's important: "models I can date??"

Good developers might be rare, but they're not hard to find. They are, however, hard to woo. You know the drill on how to woo them, it's just inconvenient/hard/expensive. But at least it's pretty well laid out.

Nice analogy. I'm hoping to find a girl that doesn't yet realize she's pretty enough to be a model, and hasn't yet developed that diva attitude ;)

The best documentation is the code itself. Check out the book Clean Code for great details.

I heartily agree that good code makes sense on it's own.

One of the things which good code and inline documentation (comments) do not communicate very well is a high level overview of the architecture of the application. In my opinion, it is better to describe such things using external documents and diagrams.

The same goes for the deployment procedures and the way the servers are laid out as well as dependencies. For example, the place I'm currently at had no documentation what-so-ever for the libraries and modules necessary to run the in-house web application and, consequently, it took us more time than it should have to figure out what needed to be installed when we moved to a new server.

Thanks for the book recommendation, seems like a great one judging by the reviews. It's always useful to learn more - will add it to my 'to read' list.

> is this a bad idea? Well, what do you bring to the table? Do Japanese people read HN or reddit, or are they hindered by the language barrier? If they are, then it's not.

Damn, ideas are never bad. As long as you do stuff, it's all good.

Yeah, Japanese people are shockingly bad at English. The idea is for Japanese users that CAN read English to provide short summaries of interesting English articles. While the Japanese media is pretty open and liberal, there are still some topics of (possible)importance that never make it into the headlines there. The US media isn't necessarily great, but if you can read English, you have access to A LOT of info to form your own opinion.

Good job on learning how to program and actually releasing something! Your site looks okay but it is kinda slow.

I suggest reading up on memcached (since you're using heroku).

Thanks for the feedback. I will check it out!