Our back-end team sometimes adds calls to a new service that they're building to test the load, a lot like this! So the idea was in the air at OkCupid, so to speak. And with such a big new piece of infrastructure, I knew there would be problems, it's just how it works. So I wanted to get something into production really quickly to have something to troubleshoot against.
We're looking for a number of engineering roles at OkCupid right now:
• web engineering manager
• mid- or senior-level iOS engineer
• junior-level android engineer
Our career site, okcupid.com/careers has links to detailed descriptions and all that, but feel free to message me directly if you want to hear what it's like working here from a front-end engineer: michael@okcupid.com
We're looking for a full time front end engineer here at OkC. I've pasted the HR'y text below, but as a front end dev at OkCupid, I can say that it's a great place to work. If you're interested in building stuff with autonomy and responsibility and push it to tons of users, you should reach out. Feel free to ping me with any questions! michael@okcupid.com
----
Do you want to work on a product that truly improves people’s lives? Do you want to work on a small team with exceptionally talented people? We’re looking for an experienced Frontend Engineer to join the OkCupid Product Team in New York City.
We're looking for enthusiastic and talented Frontend Engineers to join our growing team. You’ll be helping to make our products awesome and scalable for millions of users. You’ll get to work with a team of fantastic and fast-moving hackers to make the social web a more insightful and engaging place.
This looks great! One suggestion is that in full screen mode, the textarea doesn't stretch across the screen (it's a centered column) but since there are no borders it is hard to tell where the active area is. I think that clicking on the empty space outside of the main column could give focus to the textare, and that would have made it more clear for me.
Fascinating that there are air craft relics near the charts. I can only imagine that is part of the calibrating: so they can tell how large an aircraft is and what resolution they get for the size.
That's a holdover of the project from which I extracted these, reachably. We decided to use snake case across html css and javascript to keep things standard - feel free to judge that decision.
Given that people will most likely be using this in more traditionally camel cased situations, I think I will go through and change that this weekend. Thanks for pointing that out!
Please keep the snake_case. Think of all the things that CoffeeScript borrowed from ruby while omitting the snake_case. We aren't that far from being able to write most frontend code with snake_case. All it would take is a Backbone fork and a jQuery wrapper to get us most of the way there!
Totally. It's not necessarily meant to import into your project whole hog, it could just as easily have been a set of gists. So feel free to pick and choose ones that you might find useful!
