I'd love to read something describing the "perfect use cases for Mongo" from you :)
1,727 karma · joined March 28, 2007
I'd love to read something describing the "perfect use cases for Mongo" from you :)
<%= render partial: 'user, collection: @user.followed_users %>
I see (and write) errors like this all the time. Turning :syntax on saves me a browser refresh/compile cycle/spec run every time. Not sure if I'd need a rigorous test to tell me how helpful it is :)Dropping out was one of the best choices I've ever made but this particular thing is something that has come back to bite me in the ass several times.
Hey, I'm Federico B. and I've been working in web applications (mostly Ruby and Python) for the past 6 years. Some of the startups I've worked for are Art.sy, Mentez/Paymentez and MessageParty (YC10). I've participated in the Google Summer of Code (student and mentor) and in the Ruby Summer of Code (student).
I'm a generalist that leans more towards the backend of applications.
This week I launched my two newest personal projects:
My GitHub account is: https://github.com/febuiles
My personal website is: http://mheroin.com
You can contact me at federico@mheroin.com or @febuiles.
Caveat: This works as long as you many small customers. If you have a few large customers you can go for the customization route and just charge them a lot to make it worth the extra effort.
If you're trying to sell something directly to people (especially physical good or stuff where you don't get a trial) I'd try to stay away from them. They seem handy for URL shorteners and techie stuff.
1. "Give you a heads up on the kinds of things likely to come up for you specifically at interview".
2. "Let you ask us any questions you might have about YC".
It was a 5-10 minutes thing.
That Google description is amazing and it gives me a skeleton to work with. Thanks!
I hope you don't mind but I'll be stealing your art critic analogy :)
PS: Calling someone "idiot" is never a good way to start a discussion. Especially when you're wrong.
This a hundred times! The majority of us are probably working on web-related stuff that usually does not need a lot of CompSci on a daily basis. Picking out an fancy algorithm or a niche data structure and implementing it in a language you're just dabbling with can be a great way to learn a bunch of new stuff in a couple of hours. Set two hours to do this once a week and you'll be amazed at how fast you end up understanding new concepts.
I think you imply in your comment that "self-motivated exercise" is better than "externally facilitated". If that is true then we can start worrying less about selling the idea of exercising and more about thinking how to motivate a depressed individual.
On the other hand, if both cases of exercising offered the same results then we could say that it's not the motivation but the exercise itself who's helping us.
Seeing if it was published from Twitter for Blackberry, Tweetbot for Mac or EventualTweet tells me a lot about yourself as a person (and believe me, stuff like this makes/breaks relationships).
Do you have facts that support this or is this your opinion?
This is a great idea. Check the Humble Bundle's (http://www.humblebundle.com/) sliders at the bottom of the page to see how they handle their "Humble Tip", maybe you guys can do something similar.
I imagine Dell must suffer from the same problem on their online stores.
In the past I've helped a couple of people like yourself and some of the tips I can think of right now are:
* Use something like oDesk to keep track of the worked hours (at least in the beginning). You'll see screencaps of what they were doing every 5-10 minutes so you know you're being billed for real work.
* Get his/her contact info. (Skype, IM, phone) and keep in touch during the beginning to make sure everything's going fine.
* Use something like Pivotal Tracker, Basecamp or any other PM tool so you know at every moment where the project stands at.
* Try to talk to the person more than once a week if possible, don't let them go rogue.
* Only hire reputable people (either through something like the oDesk reputation system or GitHub account).
* Set them up with small/test projects before giving them the full thing. A 1-2 week assignment will help you both get acquainted and you'll know if you want them to be working on your stuff. Pay them for this!
My email's on my profile, if I can be of any help just drop me a line.