Are the posted questions getting worse?
-
Jeff Moden (11/13/2015)
jasona.work (11/13/2015)
Whhoooo!!!*I* nearly got singed by this reply: http://www.sqlservercentral.com/Forums/FindPost1736339.aspx
Not that I blame Jeff, he's probably had the "joy" of interviewing people like the OP...
I'm curious... How did you almost get singed by my response?
Well, Jeff, there was plenty of heat coming off that post. Sure you didn't use your pork chop launcher to send it?
-
Ah... the "blood in my eyes" caused me to misread Jason's post. I thought he meant something else.
Yes. It was a hot post and I didn't really mean to go all JC on that guy and sorry for going out of character but enough is enough. As Jason said, the interviews I've been conducting have been especially irritating. Simple pork chops were too good to use on that one especially since it was a test and he used the word "urgent".
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
To explain some of my extreme frustration in the "developers" that I've been interviewing over the last decade, the following blog post is a great example of the type of people that I've had to interview.
http://enterprisecraftsmanship.com/2015/11/11/is-sql-a-good-place-for-business-logic/
Let's see...
Improperly designed table... check.
Virtually no knowledge of T-SQL demonstrated (doesn't even know what a CASE statement is)... check.
No knowledge of how a view works (confirmation of no T-SQL knowledge)... check.
Improperly designed data model the whole article is based on... check.
Typical thinking that a single row return isn't a "set" leading to not knowing how a view works... check.
Ring-knocker attitude confirmed by attempts to justify it all by saying he used to be a database developer... check.
Typical know-it-all chip on the shoulder... check.
Yeah.... :blink::sick: NEXT!
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
And now for something completely different...
I think the guy on the right, in the red Hawaiian shirt, might be Steve...
http://space.io9.com/a-flock-of-hawaiian-shirts-invaded-the-space-station-1730976936
:hehe::hehe:
-
Jeff Moden (11/13/2015)
Ah... the "blood in my eyes" caused me to misread Jason's post. I thought he meant something else.Yes. It was a hot post and I didn't really mean to go all JC on that guy and sorry for going out of character but enough is enough. As Jason said, the interviews I've been conducting have been especially irritating. Simple pork chops were too good to use on that one especially since it was a test and he used the word "urgent".
Yeah, looking at it, I probably should've popped a couple "hehe" smileys on it.
-
jasona.work (11/14/2015)
And now for something completely different...I think the guy on the right, in the red Hawaiian shirt, might be Steve...
:hehe::hehe:
Nah... Steve has better legs than that. 😉
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
Jeff Moden (11/14/2015)
To explain some of my extreme frustration in the "developers" that I've been interviewing over the last decade, the following blog post is a great example of the type of people that I've had to interview.http://enterprisecraftsmanship.com/2015/11/11/is-sql-a-good-place-for-business-logic/
Let's see...
Improperly designed table... check.
Virtually no knowledge of T-SQL demonstrated (doesn't even know what a CASE statement is)... check.
No knowledge of how a view works (confirmation of no T-SQL knowledge)... check.
Improperly designed data model the whole article is based on... check.
Typical thinking that a single row return isn't a "set" leading to not knowing how a view works... check.
Ring-knocker attitude confirmed by attempts to justify it all by saying he used to be a database developer... check.
Typical know-it-all chip on the shoulder... check.
Yeah.... :blink::sick: NEXT!
The original blog entry itself is bad enough. The comments were mostly at least as bad (I think two people had something useful to say), or even worse (which surprised me), and the responses to them convinced me that he knows nothing about anything but thinks he knows it all. Anyone with that degree of arrogance combined with that level of ignorance is unemployable, bound to be a disruptive influence in any sensible working environment. I was tempted to join in incandescently, but managed to restrict myself to telling him that multirow results are actually very common in OLTP apps (using retail sales of music recordings as the obvious example) without actually telling him he's shown himself to be an incompetent ignorant arrogant prat who would be an asset to no imaginable enterprise with a requirement for programming.
Tom
-
I am getting seriously tired of the lack of thought and understanding evidenced by recent questions from certain individuals. Is a little bit of independent work and research really too much to ask?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
GilaMonster (11/14/2015)
I am getting seriously tired of the lack of thought and understanding evidenced by recent questions from certain individuals. Is a little bit of independent work and research really too much to ask?According to current "professional's" standards, yes it is. 🙁
-
TomThomson (11/14/2015)
Jeff Moden (11/14/2015)
To explain some of my extreme frustration in the "developers" that I've been interviewing over the last decade, the following blog post is a great example of the type of people that I've had to interview.http://enterprisecraftsmanship.com/2015/11/11/is-sql-a-good-place-for-business-logic/
Let's see...
Improperly designed table... check.
Virtually no knowledge of T-SQL demonstrated (doesn't even know what a CASE statement is)... check.
No knowledge of how a view works (confirmation of no T-SQL knowledge)... check.
Improperly designed data model the whole article is based on... check.
Typical thinking that a single row return isn't a "set" leading to not knowing how a view works... check.
Ring-knocker attitude confirmed by attempts to justify it all by saying he used to be a database developer... check.
Typical know-it-all chip on the shoulder... check.
Yeah.... :blink::sick: NEXT!
The original blog entry itself is bad enough. The comments were mostly at least as bad (I think two people had something useful to say), or even worse (which surprised me), and the responses to them convinced me that he knows nothing about anything but thinks he knows it all. Anyone with that degree of arrogance combined with that level of ignorance is unemployable, bound to be a disruptive influence in any sensible working environment. I was tempted to join in incandescently, but managed to restrict myself to telling him that multirow results are actually very common in OLTP apps (using retail sales of music recordings as the obvious example) without actually telling him he's shown himself to be an incompetent ignorant arrogant prat who would be an asset to no imaginable enterprise with a requirement for programming.
Imagine dozens more just like him and you'll truly understand the frustrations I've had during interviews of supposedly senior Developers and DBAs in the last several years. I'm really trying to not get a mean streak because of it especially when these moroffs think they're worth more than 6 figures. The really sad part is that a lot of companies don't know how to interview folks and end up hiring such arrogant sots.
I suppressed the urge to make any comment on that thread because it would be totally useless. I just hope newbies don't read his crap.
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
GilaMonster (11/14/2015)
I am getting seriously tired of the lack of thought and understanding evidenced by recent questions from certain individuals. Is a little bit of independent work and research really too much to ask?Heh... must be El Nino and the recent set of super moons. 😛
Nah... can't be that... it's been going on since even before forums began.
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
Jeff Moden (11/14/2015)
GilaMonster (11/14/2015)
I am getting seriously tired of the lack of thought and understanding evidenced by recent questions from certain individuals. Is a little bit of independent work and research really too much to ask?Heh... must be El Nino and the recent set of super moons. 😛
Nah... can't be that... it's been going on since even before forums began.
You forgot the "r" in the word after super. 😛
-
Luis Cazares (11/14/2015)
Jeff Moden (11/14/2015)
GilaMonster (11/14/2015)
I am getting seriously tired of the lack of thought and understanding evidenced by recent questions from certain individuals. Is a little bit of independent work and research really too much to ask?Heh... must be El Nino and the recent set of super moons. 😛
Nah... can't be that... it's been going on since even before forums began.
You forgot the "r" in the word after super. 😛
Touche. I hear you on that one. The original topic of the thread is still so very relevant today.
-
Ed Wagner (11/16/2015)
Luis Cazares (11/14/2015)
Jeff Moden (11/14/2015)
GilaMonster (11/14/2015)
I am getting seriously tired of the lack of thought and understanding evidenced by recent questions from certain individuals. Is a little bit of independent work and research really too much to ask?Heh... must be El Nino and the recent set of super moons. 😛
Nah... can't be that... it's been going on since even before forums began.
You forgot the "r" in the word after super. 😛
Touche. I hear you on that one. The original topic of the thread is still so very relevant today.
I will be the first to admit I am not the smartest person, but at least I try to ask questions by providing requested information with my try at the problem. When answering questions, I try to get the person to show at least a little work but usually they do not.
-
Jeff Moden (11/14/2015)
To explain some of my extreme frustration in the "developers" that I've been interviewing over the last decade, the following blog post is a great example of the type of people that I've had to interview.http://enterprisecraftsmanship.com/2015/11/11/is-sql-a-good-place-for-business-logic/
Let's see...
Improperly designed table... check.
Virtually no knowledge of T-SQL demonstrated (doesn't even know what a CASE statement is)... check.
No knowledge of how a view works (confirmation of no T-SQL knowledge)... check.
Improperly designed data model the whole article is based on... check.
Typical thinking that a single row return isn't a "set" leading to not knowing how a view works... check.
Ring-knocker attitude confirmed by attempts to justify it all by saying he used to be a database developer... check.
Typical know-it-all chip on the shoulder... check.
Yeah.... :blink::sick: NEXT!
I think it's perfectly correct to say, he should not be implementing business logic
in SQL.I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.
Viewing 15 posts - 51,376 through 51,390 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply