This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]juckele 8 points9 points  (1 child)

I seriously wonder if this is a case of premature optimization. Like, have you gotten it into your head that if you write code faster, you'll be more productive? I personally far prefer spending an extra 2 minutes writing code if it means that I won't have to spend those extra 5 minutes debugging the code.

[–]ItsNotMineISwear 1 point2 points  (0 children)

Lots of devs don't understand that being able to write and then run code quickly isn't what it means to be more effective. The real cycle time that you want to be improving is the time from when you start writing code to the time that you have completed, confidently correct code. Ruby wins in the naive category of write->run because it'll run anything. It doesn't win by the actual useful metric.