Isaac Sukin

Recent discussion sparked by opposition to the SOPA and PIPA bills has mostly been along the lines of "piracy is bad because it hurts the entertainment industries, but SOPA and PIPA go too far..." I agree with Jonathan Coulton that statements like this make too many unproven assumptions. So let's start from the beginning.

Assumption 0: People should pay money for art

I participated in my first (!) hackathon this weekend, a 48-hour student-run event at UPenn known as PennApps Hackathon. A friend and I wrote UnStock.Me, a stock trading game that -- at one point at least -- was intended to be educational. "Codecademy for the stock market" was the original idea, which we intentionally chose because it wouldn't take very long. We used the extra time to sleep and attend rush events for our fraternity (Phi Kappa Psi).

I talk to a lot of startups. I have a lot to say about what (not) to do if you are on the hiring side of this exchange, but for now I'll cover the minimum set of information you should be prepared to discuss if you want to hire a developer for your early-stage company. This is the first real interaction you'll have with a potential coworker. If you struggle with convincing someone to join your company, you can bet you'll struggle with convincing someone to buy your product or service, so you should be prepared with the information a potential hire will want to know. These are questions I will pretty much always ask you about your startup in an interview, and they're pretty similar to what a VC would want to know. When I say "I" below what I really mean is "any developer" but it's more convenient to write in the first person.

I'm writing a game in JavaScript for fun (I'm almost done, it'll be out within a few days). I've written dozens of games in traditional desktop languages, and I've written a lot of JavaScript designed to make user interfaces prettier, and I've even written some useful JS tools -- but this is the first time I've written a full application in JS complete with complex hierarchical entities. That is to say that I've never had to care much about the fact that JS more or less supports OO architectures before. I could have made this an opportunity to learn about OOP in JS, but I didn't. Instead I wrote the game basically without using (custom) objects at all, resulting in some redundancy and confusion. I did this because it was fast and easy and I already knew how to do it. The code's a mess, but so what? It works. It's good enough. I had fun, and I'm about to ship.

But I have this little note at the top of main.js:

Facebook hasn't switched everyone to the new Timeline profiles yet, but they will soon.