- Devops / Developer minded SysAdmin: this is a very important role, PUPPET, Chef, AWS, Linux, LXC, OpenVZ. Xen, VMWare, you should just have this immense desire to automate and simplify everything, and be a product person, plan, implement and ship - not a maintainer that lives in their cave until things crash, and apply one off server tweaks.
- Frontend Developer: HTML, CSS, Coffeescript - Familiarity with Node/Ruby/Mongo/Mysql, cool github projects is a plus, have to have your own website when we click your link, it should make us want to hire you.
- Backend Developer: Go, Node,Python,Ruby,Coffeescript, MongoDB, RabbitMQ are the things we use. More you know these, the better. If you miss some, don't worry, if you have a strong OOP background, and designing/working on large scale apps is your thing, just drop me an email.
We're open for remote, part time or full time in San Francisco. Only thing we don't want is that you have multiple clients. You can be a student or very experienced individual, and work for Koding 20 hours a week, or work a day or two. You just shouldn't be managing multiple clients and not show up for Koding because your other client had emergency. We want Koding to be the only thing you think about, when you're not working, when you go to sleep, when you wake up.
At this stage we're more willing to have VERY experienced developers, and we're very generous with rates. Our current freelancers have stocks in the company, we don't favor in house developers (alright, maybe just a little :)). Some of our freelancers make more than those are in the office. Your location has no significance to us, just your work. If your work is awesome, your compensation is equally awesome.
@GulA Thanks for your wisdom (let's reuse this typical i-know-it-all-and-you-dont approach). We're not scaling, if you read the post carefully, you will see that we're looking for the 5th member, and the word 'best' is used correctly. I won't provide additional reading for you, because I don't think you will read them.
Basically yes. After 10th hire, nobody can hire with a blog post like this, for reasons you've stated, plus, there won't be room for co-founder minded, entrepreneurial folks anymore.
awesome. it's not bridge, it's rosetta stone.. this will end religious wars between languages :) will bring them together.. now we can use haskell for X ruby for Y and Z for T. distribute them to different servers. very cool.
thanks for responding, it's nice of you to acknowledge it as a bug, and say you're working on it.
> First of all, writing bug reports to Hacker News is usually a bit like complaining about the government at a bus stop.
just a little note on this one, i've made clear in my original writing this is not hate and i sent an email to substack, and ryan to some others i know. i guess i will send you an email next time as well.
not filing as a bug: you are right, i should have done that.
Buffer<->string conversion is WAY too expensive in Node: yes it is, hope you can make this way better, because we don't want to hit cpu each time we pull data from a e.g. database.
writing it to hackernews/stackoverflow: it's because i'm asking for solutions outside of nodejs domain, varnish,nginx or any other way this issue can be worked around. i'm sure you understand. and this was quite helpful as we're now deploying a few varnish and nginx servers to mitigate this problem.
Sorry if my response was a bit overly strong. I know you're a good guy and we all just want these things to work well. I wasn't offended, just a bit confused by the results that weren't matching what I was seeing.
Of course, poking a bit further showed that converting a 16MB string to a buffer actually is quite expensive. You can avoid this by using buffers directly when you're serving files (or better yet, just pipe a fs.ReadStream directly into the response, so it'll stream it as it reads from disk, and buffer as little as possible.)
i wasn't saying nginx is bad (nginx is awesome). i just wouldn't want to deploy and configure nginx with my app, if i can avoid it. in fact i got an awesome suggestion over at stackoverflow, that put the usage down to 0.3% http://d.pr/dXVR
If it's an app you in tend to package up, or is portable, that might be an acceptable solution, but in the long term, using Nginx or Varnish (or even Apache) is likely the better answer, unless it is your objective to build a static file server in Node.
Otherwise, even if you can speed it up, and/or minimize its memory usage, you're still wasting cycles and memory in your app that needn't be spent on it. To a point, this is perfectly fine, but at some point, you're (hopefully) going to want to scale, and I promise that this is the first thing you'll want to look at.
