Is it Sequel or S Q L Server, Interview Gripes
-
Nishant Sivakumar wrote:
While most people I know say Sequel Server, I've heard people say EsQueueEl Server too - specially in India. Does it really matter what they say? Most people say C-Sharp, a few say C-Hash, and maybe there are a few odd people who say C-Pound.
I think this is a case of "You say potato and I say po-tah-to". :)
Nishant Sivakumar wrote:
I always say Hash-Include for #include and Hash-Using for #using
I say "Pound Include" and "Pound Using". Americans call the # on a phone "Pound". Sometimes we call # a "Number" sign. For example, #1 is "Number 1". I find it interesting how different cultures speaking the same language have all sorts of little deviations. This is probably a factor on how totally different languages evolve.
-
"include" "using" If i think there's danger of confusion, i'll say something like "pound-include", but usually it's not necessary.
----
Shog9 wrote:
"include" "using" If i think there's danger of confusion, i'll say something like "pound-include", but usually it's not necessary.
In C++,
using namespace somensdoesn't have the # before using, but#using <some.dll>has it. So sometimes if you don't specify that (either hash or pound), it may confuse some people. Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. -
Shog9 wrote:
"include" "using" If i think there's danger of confusion, i'll say something like "pound-include", but usually it's not necessary.
In C++,
using namespace somensdoesn't have the # before using, but#using <some.dll>has it. So sometimes if you don't specify that (either hash or pound), it may confuse some people. Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications.Nishant Sivakumar wrote:
In C++, using namespace somens doesn't have the # before using, but #using has it. So sometimes if you don't specify that (either hash or pound), it may confuse some people.
Perhaps. But i still think it's obvious from the context - after all, you'd never say "pound-using namespace ...". That said, i've done a lot less collaborative C# stuff, so haven't had the opportunity to really develop a feel there. And before you start, let's just not get into any discussions of VB terminology. The Lounge really isn't the place to exercise Chris's vulgarity filter... ;)
----
-
Just think how funny it'd be if we tried to pronounce all acronyms as words. Indigo would be Wicuff, and Avalon would be Wipuff. MFC would be Mofak (sorry:-O). STL would be Stell, ATL would be Attel etc. Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications.I like pronouncing acronyms - it's fun to see how ridiculous they sound. But that's probably from a Defense employment background; they like acronyms that are easy to say. My favorite was SFIR (siffer). We took the RIG from Minuteman, gave it a new name, and voila - SFIR was borne! Officially, it stood for Specific-Force-Integrating Rate gyro. But the engineers who named it told me their original private name was Same F*&^%ng Instrument, Renamed.:-D Who says engineers have no sense of humour?;P "...a photo album is like Life, but flat and stuck to pages." - Shog9
-
Shog9 wrote:
You heathen bastard.
If you like that, then you'll love my post on Windows "Vista" pronunciation! :-D http://www.codeproject.com/lounge.asp?msg=1469096&mode=all&userid=40739#xx1469096xx[^]
-
I have been developing applications using SQL Server for over ten years, and I have ALWAYS called it Sequel Server... not spelled out s q l server. Sequel is elegant, it rolls off the tongue. I read in a sidebar in one of my old database programming with VB 4 books a little history of the word and proper pronunciation, and the authors concurred that it was appropriate to call it 'sequel' as the original Sequel programming language was long dead. Every Microsoft employee I have ever met calls the product Sequel Server, and it is their damn product, if they don't know how to say it, who does? What does the rest of the community think? S Q L Server or Sequel Server? Whenever I hear someone say S Q L Server... I think 'Newbie'. In addition to saying Sequel, I also have a huge gripe with wannabes using an acronym in spoken English as opposed to saying what it is they are trying to say in the first place. I say all this because I had a telephone interview today for a position roughly 50% SQL DBA, the other half maintenance and development of new and existing C# web based applications. In the interview, I was struck by the amount of questions involving the use of said acronyms, instead of focusing on object oriented programming methodologies, use of best practices in coding, etc. Nothing about development methodologies, documentation, configuration management, just "Do you know what AWE Is?" "Do you know what IDLASM is?," and a bunch of other esoteric minutia, to which I simply replied, "Nope." I actually had a clue, but in the past when I have gotten these questions, it was because the person asking them didn't have a clue. The last straw in this interview: the majority of my ASP.NET development experience (about 4000-5000 hours worth) was spent developing IBuySpy Portal & DotNetNuke modules. The incumbent interviewer told me that at his particular company they didn't embrace such open source projects. Furthermore, they were in the planning stages of purchasing a 'real,' 'enterprise grade' CMS, and I would not be able to use such petty, insignificant tools in my role as lead ASP.NET web developer there. He didn't exactly use the words petty or insignificant, but he may as well have with his condescending tone. I was reminded of Scott Adam's writing in the Dilbert Principle where he discusses how to properly train ones replacement, in how it's very important to leave out that one important detail about ones job to ones replacement, such that when the s#$t hits the fan, everybody wistfully thinks back to w
Sequel, because it's what other people say. I worked for some time with someone who insisted on calling C++ 'C double plus'. That always griped me. Christian Graus - Microsoft MVP - C++
-
Shog9 wrote:
You heathen bastard.
If you like that, then you'll love my post on Windows "Vista" pronunciation! :-D http://www.codeproject.com/lounge.asp?msg=1469096&mode=all&userid=40739#xx1469096xx[^]
Joshua Quick wrote:
If you like that, then you'll love my post on Windows "Vista" pronunciation!
Yeah, you're dead wrong on that one too. :laugh:
----
-
Sequel, because it's what other people say. I worked for some time with someone who insisted on calling C++ 'C double plus'. That always griped me. Christian Graus - Microsoft MVP - C++
Christian Graus wrote:
'C double plus'
:doh: That's just plain sad.
----
-
Sequel, because it's what other people say. I worked for some time with someone who insisted on calling C++ 'C double plus'. That always griped me. Christian Graus - Microsoft MVP - C++
Christian Graus wrote:
I worked for some time with someone who insisted on calling C++ 'C double plus'.
:omg: Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. -
Just think how funny it'd be if we tried to pronounce all acronyms as words. Indigo would be Wicuff, and Avalon would be Wipuff. MFC would be Mofak (sorry:-O). STL would be Stell, ATL would be Attel etc. Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications.Nishant Sivakumar wrote:
Indigo would be Wicuff,
Ah - because it's WCF. I was confused at first. Christian Graus - Microsoft MVP - C++
-
Sequel, because it's what other people say. I worked for some time with someone who insisted on calling C++ 'C double plus'. That always griped me. Christian Graus - Microsoft MVP - C++
Christian Graus wrote:
'C double plus'
That's pretty lame. I keep waiting for someone to call it "increment c". :rolleyes: BW
If you're not part of the solution, you're part of the precipitate.
-- Steven Wright -
Christian Graus wrote:
'C double plus'
That's pretty lame. I keep waiting for someone to call it "increment c". :rolleyes: BW
If you're not part of the solution, you're part of the precipitate.
-- Steven Wrightbrianwelsch wrote:
I keep waiting for someone to call it "increment c".
Or even post increment C. :) Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. -
brianwelsch wrote:
I keep waiting for someone to call it "increment c".
Or even post increment C. :) Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications.:-D BW
If you're not part of the solution, you're part of the precipitate.
-- Steven Wright -
Just think how funny it'd be if we tried to pronounce all acronyms as words. Indigo would be Wicuff, and Avalon would be Wipuff. MFC would be Mofak (sorry:-O). STL would be Stell, ATL would be Attel etc. Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications.Nishant Sivakumar wrote:
Indigo would be Wicuff, and Avalon would be Wipuff.
:~
Nibu thomas Software Developer Faqs by Michael dunn
-
"include" "using" If i think there's danger of confusion, i'll say something like "pound-include", but usually it's not necessary.
----
I second that. (period) "#" is like punctuation, (comma) it shouldn't be pronounced, (comma) unless maybe you're telling someone what to type. (period) See how annoying this would be? (question) Almost as annoying as VB programmers calling braces {} "squigglies". :laugh:
- S 50 cups of coffee and you know it's on!
-
I second that. (period) "#" is like punctuation, (comma) it shouldn't be pronounced, (comma) unless maybe you're telling someone what to type. (period) See how annoying this would be? (question) Almost as annoying as VB programmers calling braces {} "squigglies". :laugh:
- S 50 cups of coffee and you know it's on!
Steve Echols wrote:
Almost as annoying as VB programmers calling braces {} "squigglies"
Please... nothing is that annoying! :laugh:
"What classes are you using ? You shouldn't call stuff if you have no idea what it does"
Christian Graus in the C# forumled mike
-
I have been developing applications using SQL Server for over ten years, and I have ALWAYS called it Sequel Server... not spelled out s q l server. Sequel is elegant, it rolls off the tongue. I read in a sidebar in one of my old database programming with VB 4 books a little history of the word and proper pronunciation, and the authors concurred that it was appropriate to call it 'sequel' as the original Sequel programming language was long dead. Every Microsoft employee I have ever met calls the product Sequel Server, and it is their damn product, if they don't know how to say it, who does? What does the rest of the community think? S Q L Server or Sequel Server? Whenever I hear someone say S Q L Server... I think 'Newbie'. In addition to saying Sequel, I also have a huge gripe with wannabes using an acronym in spoken English as opposed to saying what it is they are trying to say in the first place. I say all this because I had a telephone interview today for a position roughly 50% SQL DBA, the other half maintenance and development of new and existing C# web based applications. In the interview, I was struck by the amount of questions involving the use of said acronyms, instead of focusing on object oriented programming methodologies, use of best practices in coding, etc. Nothing about development methodologies, documentation, configuration management, just "Do you know what AWE Is?" "Do you know what IDLASM is?," and a bunch of other esoteric minutia, to which I simply replied, "Nope." I actually had a clue, but in the past when I have gotten these questions, it was because the person asking them didn't have a clue. The last straw in this interview: the majority of my ASP.NET development experience (about 4000-5000 hours worth) was spent developing IBuySpy Portal & DotNetNuke modules. The incumbent interviewer told me that at his particular company they didn't embrace such open source projects. Furthermore, they were in the planning stages of purchasing a 'real,' 'enterprise grade' CMS, and I would not be able to use such petty, insignificant tools in my role as lead ASP.NET web developer there. He didn't exactly use the words petty or insignificant, but he may as well have with his condescending tone. I was reminded of Scott Adam's writing in the Dilbert Principle where he discusses how to properly train ones replacement, in how it's very important to leave out that one important detail about ones job to ones replacement, such that when the s#$t hits the fan, everybody wistfully thinks back to w
kennster wrote:
"Do you know what IDLASM is?,"
I would have asked him, "What is that?" ;P (not sure if that was just a typo from you)**
xacc.ide-0.1.3.14 - Now with syntax support for PowerShell
xacc.ide-0.1.3.13 source code**
-
Just think how funny it'd be if we tried to pronounce all acronyms as words. Indigo would be Wicuff, and Avalon would be Wipuff. MFC would be Mofak (sorry:-O). STL would be Stell, ATL would be Attel etc. Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications.Nishant Sivakumar wrote:
Just think how funny it'd be if we tried to pronounce all acronyms as words.
What a SNAFU that would be! :)
"What classes are you using ? You shouldn't call stuff if you have no idea what it does"
Christian Graus in the C# forumled mike
-
I have been developing applications using SQL Server for over ten years, and I have ALWAYS called it Sequel Server... not spelled out s q l server. Sequel is elegant, it rolls off the tongue. I read in a sidebar in one of my old database programming with VB 4 books a little history of the word and proper pronunciation, and the authors concurred that it was appropriate to call it 'sequel' as the original Sequel programming language was long dead. Every Microsoft employee I have ever met calls the product Sequel Server, and it is their damn product, if they don't know how to say it, who does? What does the rest of the community think? S Q L Server or Sequel Server? Whenever I hear someone say S Q L Server... I think 'Newbie'. In addition to saying Sequel, I also have a huge gripe with wannabes using an acronym in spoken English as opposed to saying what it is they are trying to say in the first place. I say all this because I had a telephone interview today for a position roughly 50% SQL DBA, the other half maintenance and development of new and existing C# web based applications. In the interview, I was struck by the amount of questions involving the use of said acronyms, instead of focusing on object oriented programming methodologies, use of best practices in coding, etc. Nothing about development methodologies, documentation, configuration management, just "Do you know what AWE Is?" "Do you know what IDLASM is?," and a bunch of other esoteric minutia, to which I simply replied, "Nope." I actually had a clue, but in the past when I have gotten these questions, it was because the person asking them didn't have a clue. The last straw in this interview: the majority of my ASP.NET development experience (about 4000-5000 hours worth) was spent developing IBuySpy Portal & DotNetNuke modules. The incumbent interviewer told me that at his particular company they didn't embrace such open source projects. Furthermore, they were in the planning stages of purchasing a 'real,' 'enterprise grade' CMS, and I would not be able to use such petty, insignificant tools in my role as lead ASP.NET web developer there. He didn't exactly use the words petty or insignificant, but he may as well have with his condescending tone. I was reminded of Scott Adam's writing in the Dilbert Principle where he discusses how to properly train ones replacement, in how it's very important to leave out that one important detail about ones job to ones replacement, such that when the s#$t hits the fan, everybody wistfully thinks back to w
So I guess for me it comes down to this. What's going to actually put food on your plate? Saying yes, I know wat ILDASM (was your mispelling on purpose?) is and I know why you would use it here's an example. Might actually feed your family. However, dicing over pronunciation and and acronyms just seems a tad ... well it makes me think you are an Oakland Raiders fan. (Now that's not a slam at you nor is it a slam at true Raider Fans. True Raider Fans will know exactly who Howie Long is and exactly how great he was. "Raider Fans" probably cannot name one player on the O-Line or the D-Line nor could they probably spell Raider.) I guess for me I'm sitting here thinking. If I asked someone that's been using .Net for 5000+ hours what ILDASM was and they said, "Nope" I'd be a bit inclined to stamp their application with "Nope" when I was done with the interview. Do you understand what I'm saying? This isn't an attack on you either. I'm just trying to answer your question a bit. Having said that and having spent some time with Microsoft Employees I've met several that would cane you publicly for calling it sequel and who will inform you on the spot that it is S Q L for structured query language. But to me it's a small thing and I will simply use SQL "ESS-Q-L" because I was educated that SQL was structured query language. Anyway, I'd say in the future answer questions with the answers you have or know and reserve any judgements you intend to make until after you hear the offer extended but again this probably comes down to preference just as the answer to your question does. So that's all from me. - Rex
If we all used the Plain English compiler every post in the lounge would be a programming question.:cool:
Welcome to CP in your language. Post the unicode version in My CP Blog [ ^ ] now.People who don't understand how awesome Firefox is have never used CPhog. The act of using CPhog alone doesn't make Firefox cool. It opens your eyes to the possibilities and then you start looking for other things like CPhog and your eyes are suddenly open to all sorts of useful things all through Firefox. - (Self Quote)
-
I have been developing applications using SQL Server for over ten years, and I have ALWAYS called it Sequel Server... not spelled out s q l server. Sequel is elegant, it rolls off the tongue. I read in a sidebar in one of my old database programming with VB 4 books a little history of the word and proper pronunciation, and the authors concurred that it was appropriate to call it 'sequel' as the original Sequel programming language was long dead. Every Microsoft employee I have ever met calls the product Sequel Server, and it is their damn product, if they don't know how to say it, who does? What does the rest of the community think? S Q L Server or Sequel Server? Whenever I hear someone say S Q L Server... I think 'Newbie'. In addition to saying Sequel, I also have a huge gripe with wannabes using an acronym in spoken English as opposed to saying what it is they are trying to say in the first place. I say all this because I had a telephone interview today for a position roughly 50% SQL DBA, the other half maintenance and development of new and existing C# web based applications. In the interview, I was struck by the amount of questions involving the use of said acronyms, instead of focusing on object oriented programming methodologies, use of best practices in coding, etc. Nothing about development methodologies, documentation, configuration management, just "Do you know what AWE Is?" "Do you know what IDLASM is?," and a bunch of other esoteric minutia, to which I simply replied, "Nope." I actually had a clue, but in the past when I have gotten these questions, it was because the person asking them didn't have a clue. The last straw in this interview: the majority of my ASP.NET development experience (about 4000-5000 hours worth) was spent developing IBuySpy Portal & DotNetNuke modules. The incumbent interviewer told me that at his particular company they didn't embrace such open source projects. Furthermore, they were in the planning stages of purchasing a 'real,' 'enterprise grade' CMS, and I would not be able to use such petty, insignificant tools in my role as lead ASP.NET web developer there. He didn't exactly use the words petty or insignificant, but he may as well have with his condescending tone. I was reminded of Scott Adam's writing in the Dilbert Principle where he discusses how to properly train ones replacement, in how it's very important to leave out that one important detail about ones job to ones replacement, such that when the s#$t hits the fan, everybody wistfully thinks back to w
ROTFLMAO :laugh::laugh::laugh::laugh:
During the 1970s, a group at IBM's San Jose research center developed
a database system "System R" based upon, but not strictly faithful to,
Codd's model. Structured English Query Language ("SEQUEL") was designed
to manipulate and retrieve data stored in System R. The acronym SEQUEL was
later condensed to SQL because the word 'SEQUEL' was held as a trademark by
the Hawker-Siddeley aircraft company of the UKhttp://en.wikipedia.org/wiki/SQL[^]
"What classes are you using ? You shouldn't call stuff if you have no idea what it does"
Christian Graus in the C# forumled mike
