You can make shit out of gold any day, if you just try hard enough.



  •  Ok so there was a nifty video from years back about Rails vs PHP about how PHP has sql in the view files, etc and how it leads to spaghetti code.

     

    Well guess what. This project I took over from consultants... has sql... in the .erb file (html template).

     

    If you make a system foolproof, they will find a bigger fool.

     

    The code quality is basically this: There were 2 people working. A programmer with probly 3 yrs of experience under his belt who MAY have read a RoR book, and a programmer who is still in college who MAY have never coded before. How do I know? I was looking at the code and looking at the ruby books / online examples on some techniques to replace what was OBVIOUSLY bad design, and it turns out some techniques I read about were very poorly implemented, and sometimes avoidted alltogether and done 101% manually just to ensure every possible benefit RoR provides is left out, and I mean they went out of their way to make the code avoid any good RoR convention / mechanism.



  • @astonerbum said:

    I was looking at the code and looking at the ruby books / online examples on some techniques to replace what was OBVIOUSLY bad design, and it turns out some techniques I read about were very poorly implemented, and sometimes avoidted alltogether and done 101% manually just to ensure every possible benefit RoR provides is left out, and I mean they went out of their way to make the code avoid any good RoR convention / mechanism.

    They obviously just wanted to be able to show a RoR logo on their site, because it looks better then php. And they wanted average PHP code quality. Best of both worlds.



  • This sounds like what the Indian coder at the job I just left did. Supposedly a "Senior Rails developer" but... let's just say that I've seen prettier PHP code than the Rails code she wrote. But hey, it worked (kinda sorta maybe if you squint) and she was cheaper than hiring someone local.

    The PHP developers they hired to write some web services bridging a PHP web app to the Rails one wrote some pretty worthless code, too. But at least that was PHP, not Rails!



  • @astonerbum said:

    Well guess what. This project I took over from consultants... has sql... in the .erb file (html template).

    Bummer, man.  I hate it when I get sql in my 'erb.

     



  • @DaveK said:

    @astonerbum said:

    Well guess what. This project I took over from consultants... has sql... in the .erb file (html template).

    Bummer, man.  I hate it when I get sql in my 'erb.

     

     

    I know, even after you get that sql out, you still have a bad taste in your mouth.

     

    The strange thing is... They are not THAT incompetent, there are a few good decisions in the program, so I don't worry about changing their entire authentication algorithm to not store plain text in the database (they actually use a good auth library), and they didn't store credit card info in plain text in the database either, in fact we don't store cc info period, used cheddar. So it just feels like an episode of "when good programmers go bad". 



  • @DaveK said:

    @astonerbum said:

    Well guess what. This project I took over from consultants... has sql... in the .erb file (html template).

    Bummer, man.  I hate it when I get sql in my 'erb.

    You know how some people try to pronounce "sql" as a word, like "sequel"? I always react to that by pronouncing it "squeal" until they stop.



  • @Anonymouse said:

    @DaveK said:

    @astonerbum said:

    Well guess what. This project I took over from consultants... has sql... in the .erb file (html template).

    Bummer, man.  I hate it when I get sql in my 'erb.

    You know how some people try to pronounce "sql" as a word, like "sequel"? I always react to that by pronouncing it "squeal" until they stop.

    I bet you can SQL like a pig.



  • @Anonymouse said:

    You know how some people try to pronounce "sql" as a word, like "sequel"? I always react to that by pronouncing it "squeal" until they stop.
    So basically, you're an asshole.  Good to know.



  • @Anonymouse said:

    You know how some people try to pronounce "sql" as a word, like "sequel"? I always react to that by pronouncing it "squeal" until they stop.
     

    Could be worse.  A friend of mine likes to pronounce it "skull".



  •  @Anonymouse said:

    You know how some people try to pronounce "sql" as a word, like "sequel"? I always react to that by pronouncing it "squeal" until they stop.

     

    If that's your goal, I'd reach for "suckle" instead.



  • @Mason Wheeler said:

    @Anonymouse said:

    You know how some people try to pronounce "sql" as a word, like "sequel"? I always react to that by pronouncing it "squeal" until they stop.
     

    Could be worse.  A friend of mine likes to pronounce it "skull".

    I'm picturing a server that whenever someone tries to connect or query it, they get a skull made out of ascii back


  • @Anonymouse said:

    You know how some people try to pronounce "sql" as a word, like "sequel"?
     

    This one engineer I worked with always said "sequel" for sql, which I found very annoying.  Then one day I got an e-mail from him which said:

     "We are having problems with the sequel server"

    I think that may be the first time I ever really wanted to kill someone.

     

     



  • @El_Heffe said:

    @Anonymouse said:

    You know how some people try to pronounce "sql" as a word, like "sequel"?
     

    This one engineer I worked with always said "sequel" for sql, which I found very annoying.

     

    Does it bug you when they talk about goo-ids too?



  • @Anonymouse said:

    You know how some people try to pronounce "sql" as a word, like "sequel"?

    Whoever was preparing the official course materials for the MSSQL 2005 certification path ordered the narrator to pronounce it that way too. "The Sequel Server 2005..."

    Still makes me cringe each time I remember it.



  •  SQL comes from IBM's SEQUEL.  Of course, I didn't know that initially and just pronounced it "sequel" because that's how my boss said it.  Now it's a habit.



  • @El_Heffe said:

    @Anonymouse said:

    You know how some people try to pronounce "sql" as a word, like "sequel"?
     

    This one engineer I worked with always said "sequel" for sql, which I found very annoying.  Then one day I got an e-mail from him which said:

     "We are having problems with the sequel server"

    I think that may be the first time I ever really wanted to kill someone.

     

    "Sequel" has fewer syllables and rolls off the tongue easier.  I don't care if people want to pronounce each letter out-loud like some 10 year-old with Downs Syndrome trying to read Go Dog Go, but I'm going to keep pronouncing it "sequel".



  • @morbiuswilters said:

    "Sequel" has fewer syllables and rolls off the tongue easier.  I don't care if people want to pronounce each letter out-loud like some 10 year-old with Downs Syndrome trying to read Go Dog Go, but I'm going to keep pronouncing it "sequel".
     

    What he said. "Squirrel" is also acceptable.

    The real WTF on this is... how is it possible developers aren't aware of stored procedures?



  • @El_Heffe said:

    Then one day I got an e-mail from him which said:

     "We are having problems with the sequel server"

     

    Ah, that explains Transformers 2, then.

     

    (Pronounces it "squill")



  • @Watson said:

    @El_Heffe said:

    Then one day I got an e-mail from him which said:

     "We are having problems with the sequel server"

     

    Ah, that explains Transformers 2, then.

    No, this explains Transformers 2: Mark Kermode's (quite eloquent) review of that film:

    "Transformers Revenge of the Fallen, Transformers, Bad Boys, Bad Boys
    II, Armageddon, The Rock, Pearl Harbor... in a way, this is a review of
    all of Michael Bay's work.

    (also very funny) 

    @Watson said:

    (Pronounces it "squill")

    I don't understand what everyone's arguing about.  I pronounce it "sql", exactly how it's spelled.  That seems simplest to me.



  •  TRWTF is doing 101%.



  • @DaveK said:

    No, this explains Transformers 2: Mark Kermode's (quite eloquent) review of that film:

    "Transformers Revenge of the Fallen, Transformers, Bad Boys, Bad Boys
    II, Armageddon, The Rock, Pearl Harbor... in a way, this is a review of
    all of Michael Bay's work.

    (also very funny) 

    Goddammit, isn't there any new content on the web that's text anymore?   Video is fine for boobies or explosions.  I do not want to listen to some English faggot read his review for a camera. 



  • @morbiuswilters said:

    @DaveK said:

    No, this explains Transformers 2: Mark Kermode's (quite eloquent) review of that film:

    "Transformers Revenge of the Fallen, Transformers, Bad Boys, Bad Boys
    II, Armageddon, The Rock, Pearl Harbor... in a way, this is a review of
    all of Michael Bay's work.

    (also very funny) 

    Goddammit, isn't there any new content on the web that's text anymore?   Video is fine for boobies or explosions.  I do not want to listen to some English faggot read his review for a camera. 

    It haz a'splosions.

    It does not haz reading. 




  • @DaveK said:

    It haz a'splosions.

    It does not haz reading. 

     

    no boobie no watchie

    boobie may be supplied separately, if you will.



  • @dhromed said:

    @DaveK said:

    It haz a'splosions.

    It does not haz reading. 

     

    no boobie no watchie

    boobie may be supplied separately, if you will.

    google your own boobies!

     

     

     

     

    .

     

     

     

     

     

     

    .

     

     

     

     

     

     

     

     

     

     

     

    I've been waiting a loooong time to use that line. 

     



  • @morbiuswilters said:

    Goddammit, isn't there any new content on the web that's text anymore?   Video is fine for boobies or explosions.  I do not want to listen to some English faggot read his review for a camera. 
    Amen, brother.  Such is our plight as the last two people on the internet who can read.



  • @Tyler said:

     @Anonymouse said:

    You know how some people try to pronounce "sql" as a word, like "sequel"? I always react to that by pronouncing it "squeal" until they stop.

     

    If that's your goal, I'd reach for "suckle" instead.

     

     

    Awesome idea, as that's actually how you say sucker/idiot in Dutch...



  • @bstorer said:

    Amen, brother.  Such is our plight as the last two people on the internet who can read.
     

    Three.



  • @Evo said:

    @Tyler said:

     @Anonymouse said:

    You know how some people try to pronounce "sql" as a word, like "sequel"? I always react to that by pronouncing it "squeal" until they stop.

     

    If that's your goal, I'd reach for "suckle" instead.

     

     

    Awesome idea, as that's actually how you say sucker/idiot in Dutch...

     

    Here's how to tell if you're a dick by "correcting" someone's language:

    1) Did you understand what they meant to say?

    2) Did you "correct" it anyway?

    If both points apply to you, you are a dick.



  • @dhromed said:

    @bstorer said:

    Amen, brother.  Such is our plight as the last two people on the internet who can read.
     

    Three.

    Awww, he thinks he's people!



  • @blakeyrat said:

    @morbiuswilters said:

    "Sequel" has fewer syllables and rolls off the tongue easier.  I don't care if people want to pronounce each letter out-loud like some 10 year-old with Downs Syndrome trying to read Go Dog Go, but I'm going to keep pronouncing it "sequel".
     

    What he said. "Squirrel" is also acceptable.

    The real WTF on this is... how is it possible developers aren't aware of stored procedures?

    The real WTF is that you expect the existence of a technology to enforce design.  The original WTF was due to the developer not using RoR the way it is supposed to be used.  What makes you think that they would use stored procedures any better?



  • @morbiuswilters said:

    Awww, he thinks he's people!
     

    suckle.



  • @blakeyrat said:

    @Evo said:

    @Tyler said:

     @Anonymouse said:

    You know how some people try to pronounce "sql" as a word, like "sequel"? I always react to that by pronouncing it "squeal" until they stop.

     

    If that's your goal, I'd reach for "suckle" instead.

     

     

    Awesome idea, as that's actually how you say sucker/idiot in Dutch...

     

    Here's how to tell if you're a dick by "correcting" someone's language:

    1) Did you understand what they meant to say?

    2) Did you "correct" it anyway?

    If both points apply to you, you are a dick.

    I think you're the sukkel here.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.