Comments on: When techno-weenies make lame technology choices http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/ High-Availability Guru Mon, 30 Nov 2009 22:42:14 -0800 http://wordpress.org/?v=2.8.6 hourly 1 By: terry chay http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/comment-page-1/#comment-3401 terry chay Tue, 29 May 2007 20:22:23 +0000 http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/#comment-3401 - Ruby/RoR allows you to separate your code from your presentation So does any framework. So does any templating system. Oh, you mean, “forces you”? Then what about Clearsilver? - Ruby/RoR allows you to evolve your website features faster than you could with java or php Bullshit. RoR allows you to build your website from scratch faster than nearly anything. Practice has shown that it is very bad at evolving or scaling websites which is why 37signals and others build more websites instead of improving the ones they got. RoR is pretty much the worst platform for evolving website features. Just look at ActiveRecord. One consequence is that the class library is tightly bound to the table. What if I want to change the table? Oh, Migrations, you say? Yes, that's fine for small changes like what happens when a new version of Wordpress comes out, but on a federated system with a staged release, it’s laughable. - the most talented programmers have left php for Ruby/RoR. I'd like to see some names attached to this statement. If you’re so talented as a X language developer, you don’t need to leave for Ruby or any other language. You learn other languages to get ideas. The reality is Ruby on Rails is very popular in terms of book sales, but at the point PHP had Ruby’s book sales, it had the largest market share of any web development platform. The book sales come from the clever tie in as “Ruby is the language for Web 2.0” which causes Web 2.0 startups to think they need to use Ruby. But the dominant platform among successful Web 2.0 startups is PHP (by far, its probably over 50% of the top 1000 web 2.0 companies). There is only one Web 2.0 RoR app that has reached that benchmark of success, Twitter. When Ruby competed head to head with a competitive Web 2.0 space, it got its <a href="http://gigaom.com/2006/08/26/kiko-sells-for-258100/" rel="nofollow">ass kicked in</a>, badly. - Ruby/RoR allows you to separate your code from your presentation

So does any framework. So does any templating system. Oh, you mean, “forces you”? Then what about Clearsilver?

- Ruby/RoR allows you to evolve your website features faster than you could with java or php

Bullshit. RoR allows you to build your website from scratch faster than nearly anything. Practice has shown that it is very bad at evolving or scaling websites which is why 37signals and others build more websites instead of improving the ones they got. RoR is pretty much the worst platform for evolving website features.

Just look at ActiveRecord. One consequence is that the class library is tightly bound to the table. What if I want to change the table? Oh, Migrations, you say? Yes, that’s fine for small changes like what happens when a new version of Wordpress comes out, but on a federated system with a staged release, it’s laughable.

- the most talented programmers have left php for Ruby/RoR.

I’d like to see some names attached to this statement. If you’re so talented as a X language developer, you don’t need to leave for Ruby or any other language. You learn other languages to get ideas.

The reality is Ruby on Rails is very popular in terms of book sales, but at the point PHP had Ruby’s book sales, it had the largest market share of any web development platform. The book sales come from the clever tie in as “Ruby is the language for Web 2.0” which causes Web 2.0 startups to think they need to use Ruby. But the dominant platform among successful Web 2.0 startups is PHP (by far, its probably over 50% of the top 1000 web 2.0 companies). There is only one Web 2.0 RoR app that has reached that benchmark of success, Twitter. When Ruby competed head to head with a competitive Web 2.0 space, it got its ass kicked in, badly.

]]>
By: Ben Yoskovitz http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/comment-page-1/#comment-3322 Ben Yoskovitz Wed, 23 May 2007 02:13:42 +0000 http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/#comment-3322 Thanks Alex, and best of luck learning Ruby. I can tell you from a "market feel" that Ruby is certainly in big demand and contractors/freelancers such as yourself are finding ample (and well-paying) work doing Ruby development. I'd say it's a good feather to have in your programmer cap. Thanks Alex, and best of luck learning Ruby. I can tell you from a “market feel” that Ruby is certainly in big demand and contractors/freelancers such as yourself are finding ample (and well-paying) work doing Ruby development. I’d say it’s a good feather to have in your programmer cap.

]]>
By: Alex http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/comment-page-1/#comment-2861 Alex Tue, 08 May 2007 03:07:35 +0000 http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/#comment-2861 Ben, your comment has led me to much reflection. The truth is, I have absolutely nothing against Ruby. I think you made some very strong arguments to confirm your decision and I respect that. I think this is also a sign for me to break out of my PHP bubble. In one of my Top Posts, I mentioned that I would continue to learn Ruby, which I didn't. This is unfortunate as I now realize the real importance of learning and staying ahead of the curve. Good luck Ben! I hope you find a suitable person for your startup. Ben, your comment has led me to much reflection.

The truth is, I have absolutely nothing against Ruby. I think you made some very strong arguments to confirm your decision and I respect that.

I think this is also a sign for me to break out of my PHP bubble. In one of my Top Posts, I mentioned that I would continue to learn Ruby, which I didn’t. This is unfortunate as I now realize the real importance of learning and staying ahead of the curve.

Good luck Ben! I hope you find a suitable person for your startup.

]]>
By: Ben Yoskovitz http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/comment-page-1/#comment-2795 Ben Yoskovitz Sun, 06 May 2007 02:52:18 +0000 http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/#comment-2795 Alex, It's not ironic at all. If the tools we plan to build already existed, we wouldn't have problems. *grin* And don't think of it as a problem, think of it as an opportunity... I know if we put a job posting on Monster or Jobboom we'd get hundreds of resumes, but so what? That's not how you find real talent. I'm not sure what your personal beef is with Ruby, or if you just don't like that we picked it without consulting you *smile* ... but ... We picked Ruby (and Rails) for specific reasons. Fred's no slouch when it comes to understanding technology and the issues surrounding it. Neither am I (or Austin.) So we didn't pick Ruby for the heck of it or because it's the "flavor of the month." Everyone we hire, particularly at this early stage, will have a say in key issues - be they technology, marketing, sales, product roadmap, etc. That's the kind of company we're building. But decisions have to be made, and they have to be made at the right times to move the ball forward, especially for a startup trying to build well + quickly. Thank you for your continued thoughts... Alex,

It’s not ironic at all. If the tools we plan to build already existed, we wouldn’t have problems. *grin*

And don’t think of it as a problem, think of it as an opportunity…

I know if we put a job posting on Monster or Jobboom we’d get hundreds of resumes, but so what? That’s not how you find real talent.

I’m not sure what your personal beef is with Ruby, or if you just don’t like that we picked it without consulting you *smile* … but …

We picked Ruby (and Rails) for specific reasons. Fred’s no slouch when it comes to understanding technology and the issues surrounding it. Neither am I (or Austin.) So we didn’t pick Ruby for the heck of it or because it’s the “flavor of the month.”

Everyone we hire, particularly at this early stage, will have a say in key issues – be they technology, marketing, sales, product roadmap, etc. That’s the kind of company we’re building. But decisions have to be made, and they have to be made at the right times to move the ball forward, especially for a startup trying to build well + quickly.

Thank you for your continued thoughts…

]]>
By: Alex http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/comment-page-1/#comment-2769 Alex Fri, 04 May 2007 15:46:16 +0000 http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/#comment-2769 Thanks Ben, for taking the time to reply. I find it kind of ironic that a company looking to build software to simplify the hiring process, could possibly have difficulty hiring. Haha! Peut-etre je m'y prends trop d'avance... you guys just posted this yesterday ;) Ok all jokes aside, your offer seems rather interesting, minus the Ruby. I think if I weren't so biased I might have applied... maybe that's why I wrote this post ;) Either way, you clearly stated that you're open to discussion, so if that's the case, then your future Ruby Guru should help in making difficult technological choices. That's just my opinion though. Thanks Ben, for taking the time to reply.

I find it kind of ironic that a company looking to build software to simplify the hiring process, could possibly have difficulty hiring. Haha! Peut-etre je m’y prends trop d’avance… you guys just posted this yesterday ;)

Ok all jokes aside, your offer seems rather interesting, minus the Ruby. I think if I weren’t so biased I might have applied… maybe that’s why I wrote this post ;)

Either way, you clearly stated that you’re open to discussion, so if that’s the case, then your future Ruby Guru should help in making difficult technological choices.

That’s just my opinion though.

]]>
By: Ben Yoskovitz http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/comment-page-1/#comment-2763 Ben Yoskovitz Fri, 04 May 2007 10:19:56 +0000 http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/#comment-2763 Ruby is so cool, isn't that reason enough? *grin* I think Heri's thoughts on the technology make sense. And you did question in your post, "why did they choose Ruby?" So I think Heri answered that question specifically... Another reason to choose Ruby (or any technology) is that a choice makes it easier to hone in on people. Had we not made a choice, and the video was for a "Tech Guru" we would have had too generic and loose a job ad / job description. I think the bigger issue is - "they'll be looking a long time." Maybe, maybe not. And if we are looking a long time, so be it. Most of the best people aren't looking for jobs specifically. They're passive candidates. People should always be keeping their ear to the ground, and their eyes open. Since we know the type of person we want does exist, it's then our job to find them, connect with them and make them an offer they can't refuse. We need someone who is more than a coder. There are many reasons for that. We're building a core team around this person, with a team culture and future that will depend heavily on them. Fred and I already have a sense of the culture we want to develop, and some of our beliefs are also tied into what we're looking for. And who says we're looking just in Montreal? *smile* Ruby is so cool, isn’t that reason enough? *grin*

I think Heri’s thoughts on the technology make sense. And you did question in your post, “why did they choose Ruby?” So I think Heri answered that question specifically…

Another reason to choose Ruby (or any technology) is that a choice makes it easier to hone in on people. Had we not made a choice, and the video was for a “Tech Guru” we would have had too generic and loose a job ad / job description.

I think the bigger issue is – “they’ll be looking a long time.” Maybe, maybe not. And if we are looking a long time, so be it.

Most of the best people aren’t looking for jobs specifically. They’re passive candidates. People should always be keeping their ear to the ground, and their eyes open. Since we know the type of person we want does exist, it’s then our job to find them, connect with them and make them an offer they can’t refuse.

We need someone who is more than a coder. There are many reasons for that. We’re building a core team around this person, with a team culture and future that will depend heavily on them. Fred and I already have a sense of the culture we want to develop, and some of our beliefs are also tied into what we’re looking for.

And who says we’re looking just in Montreal? *smile*

]]>
By: Alex http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/comment-page-1/#comment-2757 Alex Fri, 04 May 2007 04:20:02 +0000 http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/#comment-2757 Hi Heri, Those are very good reasons to choose Ruby over PHP. Unfortunately that's not what i'm trying to discuss. It's not the technology that I question. Had they chosen Python, PHP or Lisp, I would have had the same arguments. If Paul Graham announces that he's searching for a Lisp Guru with the above requirements, it would make complete sense. I'm convinced there are some pretty proficient Ruby programmers in Montreal. That shouldn't be difficult to find. From what I understood, after viewing the video a dozen times, they are not looking for just a "guru programmer". I'll let them clarify. I could also be totally wrong ;) Hi Heri,

Those are very good reasons to choose Ruby over PHP. Unfortunately that’s not what i’m trying to discuss.

It’s not the technology that I question.

Had they chosen Python, PHP or Lisp, I would have had the same arguments.

If Paul Graham announces that he’s searching for a Lisp Guru with the above requirements, it would make complete sense.

I’m convinced there are some pretty proficient Ruby programmers in Montreal. That shouldn’t be difficult to find. From what I understood, after viewing the video a dozen times, they are not looking for just a “guru programmer”.

I’ll let them clarify. I could also be totally wrong ;)

]]>
By: Alex http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/comment-page-1/#comment-2755 Alex Fri, 04 May 2007 02:35:12 +0000 http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/#comment-2755 heh... it's cause i'm french ;) heh… it’s cause i’m french ;)

]]>
By: Barry Hess http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/comment-page-1/#comment-2754 Barry Hess Fri, 04 May 2007 02:32:43 +0000 http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/#comment-2754 "A minimum level of creativity" Every time I look at that I want to read "A _minimal_ level of creativity." That _really_ doesn't make sense. :) “A minimum level of creativity”

Every time I look at that I want to read “A _minimal_ level of creativity.” That _really_ doesn’t make sense. :)

]]>
By: heri http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/comment-page-1/#comment-2750 heri Fri, 04 May 2007 01:13:10 +0000 http://www.alexwilliams.ca/blog/2007/05/03/when-techno-weenies-make-lame-technology-choices/#comment-2750 hi Actually, Fred Ngo has a lot of experience so i trust him on this. possible answers: - Ruby/RoR leads to faster development time, so it appears one of the only possible solutions if you have a tight schedule. - Ruby/RoR allows you to separate your code from your presentation - Ruby/RoR allows you to evolve your website features faster than you could with java or php - the most talented programmers have left php for Ruby/RoR. of course I am biaised because my tool of the trade is ruby. you might be right though about the approach - ruby programmers are pretty rare in montreal. hi

Actually, Fred Ngo has a lot of experience so i trust him on this. possible answers:
- Ruby/RoR leads to faster development time, so it appears one of the only possible solutions if you have a tight schedule.
- Ruby/RoR allows you to separate your code from your presentation
- Ruby/RoR allows you to evolve your website features faster than you could with java or php
- the most talented programmers have left php for Ruby/RoR.
of course I am biaised because my tool of the trade is ruby.

you might be right though about the approach – ruby programmers are pretty rare in montreal.

]]>