Say you've raised your rates because the industry lately have been getting you A LOT OF WORK, then ask for a value that would be interesting to you($200+/h?). If the client runs away, you still have chance to get back to him after a while.
I can do:
C/C++, Ruby on Rails(with TDD/BDD), Node.js/real-time(socket.io) and front-end(html/css/javascript). I can work with the following the relational databases: postgres/mysql and nosql databases: mongodb, dynamodb, neo4j. Some devops(good unix knowledge, can set up your server with nginx/unicorn or passenger and automate with capistrano).
I currently maintain the carrierwave gem, which is a _very popular_ choice for file uploads, had a pull request accept in rails/rails... my github is: https://github.com/thiagofm
I have previously worked for a startup that got sold to one of the largest e-commerce platform in Brazil.
Just in case you want to know, I do have a computer science degree and I'm willing to tackle any hard problem that might come.
I love to do great work and I would appreciate any inquires you have to use my expertise in order to help you.
go is very fast(it's aimed at somewhere between C and C++).
it's a systems programming language, you supposedly can do anything. there's some companies already using it like soundcloud. it's awesome for api's because of it's speed.
also, it's a well thought language with many different decisions from common languages, it does not have exceptions and so on. it's an awesome language if you want to expand your mind.
Make the "sign in with facebook text" be "facebook sign in". The text is too big and it seems that both the facebook and the "get an invitation buttons" have to be of the same size in order to be aesthetically pleasing to the eye.
Hi everyone from hacker news. I'm currently a maintainer of the carrierwave gem, worked on a startup that got sold and I'm looking for a team OR people to join me in railsrumble. I can do frontend, pretty well versed with memcached and node.js also.
Charge yearly a X%(go figure it out what works best) of what you would charge one-time.
Charging a one-time fee is evil for the customer with common sense. If your service stops growing, what about the customers that already paid for it?
You don't pay for updates in a SaaS app as it's in the cloud, so... I can only truly see a recurring model working. UNLESS you know very well your userbase and you know very deeply it's the only model that would work.
São Paulo, Brazil. I'm a full stack dev(ruby/node.js).
1. $30k/y
2. $20k/y
3. $50k/y
Salary rates here sucks balls, my dream is to get clients and then freelance(I'm awesome technically, but got no contacts or whatsoever) and make what an US developer would(60-70k).
Vest his 50% equity but instead of using time, use "customers" he bought on board(or define a different way to measure his value) and decide an amount of customers he should bring in order to make it worth those 50%.
Give him them the equity that he deserve based on this performance. :)