4 ms·
I would encourage you to write the entire thing, frontend, backend, content, PR releases, etc. Two reasons: 1. You're young and still figuring out what you lo
by liyanchang 13y ago
I would encourage you to write the entire thing, frontend, backend, content, PR releases, etc.
Two reasons:
1. You're young and still figuring out what you love doing; no better time to experiment and learn. I still have fond memories over the php site I wrote in high school. You could visible tell which functions were written at the beginning of the project versus the end because you'll improve drastically. [1]
2. The project will be more successful with someone who cares for it. Hiring a contractor will make it difficult for you to maintain and improve. Contractors will also expect a specification with penalties if you need to change it. My guess is that you're still experimenting with what can best serve the community so this probably isn't a good fit for contracting as well.
[1] Recommended tech stack (optimizing for documentation and availability of help). Ruby, MongoDB, Heroku (or if ambitious, Linux on Amazon EC2 + nginx). Everything else is pretty similar so once you learn these, the concepts apply reasonably well.
p.s. If money is a concern, you should look into contacting some companies PR/DevRel people and see if they are willing to donate some compute time or services to your cause. (It's probably doing this after launch and getting a better sense of usage and will be easier to convince them that you're legit).
- curun1r 13y agoIf he's already familiar with front-end development, I'd recommend something like Meteor rather than Ruby. Because it's JavaScript, it will seem a lot more familiar than Ruby. And it will hide a lot of the complexity of client-server interaction until the point when you feel like diving into it. It's really perfect for fast prototyping and proof-of-concept sites like the poster is looking to build.
- pa5tabear 13y agoDoesn't it have major scaling problems? I've seen many recommendations that it's not yet ready for anything with complexity.
- philwelch 13y agoI generally agree with all of this. Backend is not as scary as you might assume, and it's not hard to ship something that works.
- gremlinsinc 13y agono kidding, I'm finding Angular / JS a pill compared to Laravel/Rails backends.
- lojack 13y agoAdditionally if he's looking for assistance in the backend front I'm more than willing to help out. I can't necessarily pick up a new project, but I do know how invaluable it is to have someone to bounce ideas and questions off of. I work primarily with Python and Angular at the moment, but I can provide assistance in other areas as well. OP, if you'd like to take me up on this offer just connect with me on GitHub (link in profile) and I'll shoot you a message.