3 ms·

Novice with 7 months of learning here. Quit my strategy consulting job to focus full time on learning to code, and am currently working on this project, built i

Novice with 7 months of learning here. Quit my strategy consulting job to focus full time on learning to code, and am currently working on this project, built in Rails, on Heroku (it's all in Japanese, but the concept is similar to Hacker News/Reddit) http://www.daidake.com http://www.daidake.com Is this a bad idea? Would like to hear your thoughts. I have to admit I do feel like I'm in a little bit over my head, in that once/if I start getting a lot of users, I really have no idea how to scale this thing. I figure I need to start networking to find a brain that wants to team with me. I'm glad I've learned to program though, even if at a beginner level. If this fails (I already have a previous project that was a resounding failure), I can test out new projects easily.

sebcat 14y ago
> 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.
- badatmath 14y ago
  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.
csgavino 14y ago
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).
- badatmath 14y ago
  Thanks for the feedback. I will check it out!
jrogers65 14y ago
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.
- badatmath 14y ago
  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.
  - jrogers65 14y ago
    > 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.
benjamincburns 14y ago
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.
- badatmath 14y ago
  > 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).

sebcat 14y ago

> 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.

badatmath 14y ago
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.

csgavino 14y ago

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).

badatmath 14y ago
Thanks for the feedback. I will check it out!

jrogers65 14y ago

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.

badatmath 14y ago
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.
- jrogers65 14y ago
  > 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.

benjamincburns 14y ago

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.

badatmath 14y ago
> 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).