It's just a saying I heard a long time ago from one of my professors. He probably meant it in the academic sense, i.e. the person could otherwise use that mental energy to do great research.
Huh? This is gross oversimplification of both APIs and the role of business development. The author somehow conflates deals with API integration. Not all deals (and not all deals are term sheets, whatever) result in APIs integration. Not all API integration coincides with business development activity.
I feel like people who deny the business model of app.net are trying to refute the existence and success of HBO. You don't need to operate at the scale of Facebook, Twitter or cable networks to be successful, mainly because your criteria for success are very different with a pay-for, ad-free product.
Moreover I don't need to be a victim of guns (sorry for referring to a lightning rod of an issue, but bare with me) to advocate gun control. Same way you don't have to be a developer victimized by Twitter and Facebook to think that there might be a better way.
And for the record, I did put my money where my mouth is.
My wife and I live in a ~300 square foot apartment in NYC, although we don't feel like we've got plenty of room, we never feel cramped either. Moreover, we often have people sleep over in our "living room". A lot of it is about light and how high your ceilings are.
I guess what I am saying is that the absolute minimum square footage you think you need is a malleable concept.
I like the idea, but I cannot imagine normals using it en masse. It seems so natural to those familiar with software engineering because it's basically a little language embedded into email conversations. For someone unfamiliar with computer science concepts like translation, languages, compilers, etc, it would be a formidable thing to learn and use.
I built this little app over the last few weekends. The idea was to help me to organize my thoughts for the different projects I was mulling over. I really feel like writing things down can be a great way to get to the essence of what it is you are trying to do and why.
This is just a simple realization of that idea. Implemented in Python using Heroku's Cedar stack.
Noted. I didn't mean to come off as adversarial or manipulative. This is really a conversation starter, and I rarely just write down the answer and move on.
But I do feel like it helps me learn a whole lot about the candidate without compromising that trust or condescending to them with "what's your biggest weakness?" or some such.
Since I ask this all the time, I can vouch that it rarely results in the candidate criticizing their previous employer (unless the previous employer did something truly egregious).
I admit it's a hack. Or rather, it's just a tool, like many other that helps me learn something about the candidate. So yeah, all those caveats definitely apply.
I understand why someone would hate this kind of question, but ultimately the point of any interview is to evaluate the candidate as a match for a particular role and position. I've always been told that there is not such thing as a bad candidate, only a bad fit. I find that it's helpful to think of this in those terms. Also, I really do mean that there isn't the one "correct" answer.
The conversation at the next table in NY is usually about real estate, hedge funds or some wild combination of the two. In SF, it's about the next Dropbox... for cats... on Facebook. Either way you are screwed. Every city is an echo chamber in its own right.
Well I tried to give away a meetup ticket on Twitter. You just had to be one of the next 10 people to follow me and Tweet about Turn-O-Phrase. It was a pain in the ass tracking all the followers and who said what.
Many businesses already do this. I see hundreds of SMBs running contests on Twitter every day. Usually you have to retweet and follow to enter, but there are some other rules too occasionally. It would be nice to automate that workflow and/or help them define it.
The memories of stressing out over the grad school letters are still vivid after some 8 years. But I did my homework (research with two of the letter writers and TA-ship with the other), and it paid off.
I do remember one episode when a recommendation letter was due at midnight, and I've been emailing reminders to this professor up to the hour the submission was due. He eventually replied saying that his plane was late, and he wouldn't be able to submit until 1am.
It was for a national science foundation fellowship, which I got, so I suppose the late submission was accepted in the end. Fun times.
It's one of those things that you kind of know to be true, but then it startles you when feel its impact on your own work over a long period of time. Thanks, BTW.