I think you can hate a language.. you can hate it because you hate yourself, for the things the language make you do.
Coming from a Java background, I used to bang my head on the desk everything I had to write a boilerplate code for anonymous functions/classes.. luckily, there was Intellij IDE to ease the pain.
There is a lot of bad code out there, but you shouldn't judge Ruby by a random code snippet- Ruby is just the tool, and the developer is responsible to write clean code.
I don't know what the code is trying to do with all the nested mapping.. it seems like the first 2 lines break encapsulation of the Repo model, trying to gather all the commits. This is unrelated to Ruby, it's a "bad" OO design (might be wrong, I didn't read the rest of the code)
So lets ignore that, and just rewrite from line 3 and below:
def fresh_commits(repo, n = 10)
commits = repo.heads.map do |h|
repo.commits(h.name, n).map { |c| Commit.new(c, h) }
end
commits.flatten.uniq_by(&:id).sort_by(&:committed_date).first(n)
end
Do you agree that the last line is clean & readable, even if you don't know "exactly" what "&:function_name" does?
I can value the skills of another developer. I can't value "well-connected" or "marketing/sales skills"
So if a developer comes to me with an idea, I can evaluate the partnership better- it is less risky then to go with a partner with complementary skills (not saying it's better to do it, it's just easier to figure out what you are getting into)
What is the state of Rethink db? Is it fit for production use?
In the website it stated as 1.3.2 (which imply production ready) but I think I saw some comments a month ago from you that it's not fit for production use yet.
What about secondary indexes?
Are the machines in the screencast are very weak? a simple query (get 2 rows of the dota table) running ~100ms is really slow- is it because you're using the web interface?
RethinkDB seems cool and I really want to try it in my next pet project :)
Yes -- we had an internal versioning scheme that crossed 1.0 very early on. Having different internal and external versioning schemes went against our intuition of having an open development process, so we decided to bite the bullet and keep the version post 1.0. It isn't ideal, but it's done :)
What do you mean by "twice as much experience"? Does it makes you twice as productive? or just twice as much "time"?
If you are more productive, you can try to get more- but take into consideration:
1. You should have hard evidences that you are more productive- developers tend to think that they are better/have more experience then others at their level.
2. You should know your market value outside of the company and act according to that, not just your co-workers salary.
"twice as much experience" is inaccurate. I meant "twice as much time" and I am not twice as much productive.
(1) For the experience, I have more experience than some (maybe not twice as much) for the following criterion:
- documented code/api
- always seeking to improve my coworkers' productivity (via documentation or automation)
- well designed interfaces
- fairly on time for deadlines.
Though the first 3 criterion are not really sought after by other devs.
(2) How can I find out my market value ? What are the criterion ?
You couldn't solve this kind of riddles on the net because you need to ask someone yes/no questions to figure out the story :(
So I built this site to have fun, and play with angular.js / real-time (faye)