November 9, 2017 at 12:09 pm
jasona.work - Thursday, November 9, 2017 11:58 AMLynn Pettis - Thursday, November 9, 2017 11:43 AMjasona.work - Thursday, November 9, 2017 10:35 AMSigh...
Work from home only works when the work VPN is working...
Bloody thing went down at 10:20 this morning and still isn't back up. Able to do other things that are work-related and haven't had anything come up to where I need to actually put on pants to go in (yet.)I have permission to work from home, just not doing it yet since dad is still in the hospital.
How's he doing now?
He is still in a lot of pain. That is causing him not to eat. They got his blood pressure at least stabilized, still working on pain management.
November 9, 2017 at 1:58 pm
So we had a problem updating a record in our third party product. I opened a case on the vendor's website and detailed the steps that I took to create the problem. There was a recent job change and the incorrect hours per pay period were entered in the form for the job change. The steps included correcting the most recent history record to fix the hours per pay period and entering the final annual salary so that the interface would calculate the correct hourly, weekly, and pay period salaries. When the tech assigned to the case tried to recreate the problem, she added a new job history record instead of updating the most recent job history record and entered the hourly rate instead of the annual salary as the basis for calculating the other fields. She was unable to recreate the issue. Is it any surprise, since she couldn't even follow the steps to recreate the issue? :angry:
Drew
J. Drew Allen
Business Intelligence Analyst
Philadelphia, PA
November 9, 2017 at 2:42 pm
drew.allen - Thursday, November 9, 2017 1:58 PMSo we had a problem updating a record in our third party product. I opened a case on the vendor's website and detailed the steps that I took to create the problem. There was a recent job change and the incorrect hours per pay period were entered in the form for the job change. The steps included correcting the most recent history record to fix the hours per pay period and entering the final annual salary so that the interface would calculate the correct hourly, weekly, and pay period salaries. When the tech assigned to the case tried to recreate the problem, she added a new job history record instead of updating the most recent job history record and entered the hourly rate instead of the annual salary as the basis for calculating the other fields. She was unable to recreate the issue. Is it any surprise, since she couldn't even follow the steps to recreate the issue? :angry:Drew
Sounds like most people in technical support I deal with regularly. They are in support because they can't pay attention to detail well enough to make it as a developer. 🙂
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
November 9, 2017 at 7:05 pm
Speaking of stupid people, my Debbie stopped at the store on the way home for a couple of things. There was no bottled water, no bread, and a lot of other things had been bought out to a bare shelf status. When she asked the cashier what was going on, she said "Where have you been? You haven't heard about the 2 week Northern Hemisphere blackout that NASA has predicted for November"? <headdesk><massive face palm>
Where have people like that cashier and the idiots that went nuts a bought a food cache been? That same stupid but viral email has been going around every odd year since 2011. These are the same idiots that are allowed to vote. I'm thinking that a shoelace may have a higher IQ.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 10, 2017 at 5:49 am
Sean Lange - Thursday, November 9, 2017 2:42 PMdrew.allen - Thursday, November 9, 2017 1:58 PMSo we had a problem updating a record in our third party product. I opened a case on the vendor's website and detailed the steps that I took to create the problem. There was a recent job change and the incorrect hours per pay period were entered in the form for the job change. The steps included correcting the most recent history record to fix the hours per pay period and entering the final annual salary so that the interface would calculate the correct hourly, weekly, and pay period salaries. When the tech assigned to the case tried to recreate the problem, she added a new job history record instead of updating the most recent job history record and entered the hourly rate instead of the annual salary as the basis for calculating the other fields. She was unable to recreate the issue. Is it any surprise, since she couldn't even follow the steps to recreate the issue? :angry:Drew
Sounds like most people in technical support I deal with regularly. They are in support because they can't pay attention to detail well enough to make it as a developer. 🙂
When we were hiring for our contract job, we specified "attention to details" as a must. Then we got candidates who made comments like "oh, but my skills are to focus on the high level stuff, not the little things" when we started asking technical questions on the phone interviews.
Needless to say, none of them made it past that stage.
November 10, 2017 at 5:54 am
Brandie Tarvin - Friday, November 10, 2017 5:49 AMSean Lange - Thursday, November 9, 2017 2:42 PMdrew.allen - Thursday, November 9, 2017 1:58 PMSo we had a problem updating a record in our third party product. I opened a case on the vendor's website and detailed the steps that I took to create the problem. There was a recent job change and the incorrect hours per pay period were entered in the form for the job change. The steps included correcting the most recent history record to fix the hours per pay period and entering the final annual salary so that the interface would calculate the correct hourly, weekly, and pay period salaries. When the tech assigned to the case tried to recreate the problem, she added a new job history record instead of updating the most recent job history record and entered the hourly rate instead of the annual salary as the basis for calculating the other fields. She was unable to recreate the issue. Is it any surprise, since she couldn't even follow the steps to recreate the issue? :angry:Drew
Sounds like most people in technical support I deal with regularly. They are in support because they can't pay attention to detail well enough to make it as a developer. 🙂
When we were hiring for our contract job, we specified "attention to details" as a must. Then we got candidates who made comments like "oh, but my skills are to focus on the high level stuff, not the little things" when we started asking technical questions on the phone interviews.
Needless to say, none of them made it past that stage.
Sorry, I missed what you said, my phone was vibrating so I put it on mute. I'm, uh, I'm here for the, uh, interview?
-------------------------------------------------------------------------------------------------------------------------------------
Please follow Best Practices For Posting On Forums to receive quicker and higher quality responses
November 10, 2017 at 7:20 am
I have witnessed a candidate actually answer a phone during a job interview.
November 10, 2017 at 12:36 pm
Beatrix Kiddo - Friday, November 10, 2017 7:20 AMI have witnessed a candidate actually answer a phone during a job interview.
I am not all that surprised. It seems that many people from the current generation (those in their 20s and 30s) put importance on their damn phone higher than nearly everything else in their snowflake existence. They would rather answer a phone call from their friends as not disappoint them then get through a job interview. This is exactly why I leave my phone in the car when I go in for an interview. Of course my last interview (where I was the interviewee) was nearly a decade ago now. Next August will be 10 years here for me.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
November 10, 2017 at 12:55 pm
Sean Lange - Friday, November 10, 2017 12:36 PMBeatrix Kiddo - Friday, November 10, 2017 7:20 AMI have witnessed a candidate actually answer a phone during a job interview.I am not all that surprised. It seems that many people from the current generation (those in their 20s and 30s) put importance on their damn phone higher than nearly everything else in their snowflake existence. They would rather answer a phone call from their friends as not disappoint them then get through a job interview. This is exactly why I leave my phone in the car when I go in for an interview. Of course my last interview (where I was the interviewee) was nearly a decade ago now. Next August will be 10 years here for me.
I was in an interview once, and I was mortified that I had forgotten to silence my phone beforehand and it went off. I rejected the call without even looking to see who it was. It turns out it was my brother calling to let me know that my father had passed. 🙁
Drew
J. Drew Allen
Business Intelligence Analyst
Philadelphia, PA
November 10, 2017 at 1:21 pm
drew.allen - Friday, November 10, 2017 12:55 PMSean Lange - Friday, November 10, 2017 12:36 PMBeatrix Kiddo - Friday, November 10, 2017 7:20 AMI have witnessed a candidate actually answer a phone during a job interview.I am not all that surprised. It seems that many people from the current generation (those in their 20s and 30s) put importance on their damn phone higher than nearly everything else in their snowflake existence. They would rather answer a phone call from their friends as not disappoint them then get through a job interview. This is exactly why I leave my phone in the car when I go in for an interview. Of course my last interview (where I was the interviewee) was nearly a decade ago now. Next August will be 10 years here for me.
I was in an interview once, and I was mortified that I had forgotten to silence my phone beforehand and it went off. I rejected the call without even looking to see who it was. It turns out it was my brother calling to let me know that my father had passed. 🙁
Drew
Ugh that really stinks. What horrible timing for sure. 🙁
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
November 10, 2017 at 4:46 pm
Sean Lange - Wednesday, November 8, 2017 7:19 AMAnd one line per column in the code please. 🙂
😉 Perhaps you should invest in a wider screen? 😀
Tom
November 10, 2017 at 5:07 pm
Steve Jones - SSC Editor - Wednesday, November 8, 2017 12:29 PMGuess that includes me. I like commas at the front. And code isn't prose.
That makes me recall the famous saying "Tout ce qui n'est pas verse est prose". Or :ermm: maybe it was "Tout ce qui n'est pas prose est verse".
Either way when I add your statement to that, I guess the result is that code is verse. 😛
Actually, that's not too far wrong - good code has a lot in common with good poetry (both require skilled creative effort).
But I haven't see much poetry with commas at the beginnings of lines. 😀
Tom
November 10, 2017 at 5:45 pm
TomThomson - Friday, November 10, 2017 4:46 PMSean Lange - Wednesday, November 8, 2017 7:19 AMAnd one line per column in the code please. 🙂😉 Perhaps you should invest in a wider screen? 😀
I have 3 28" screens at home, still prefer one column per line.
November 10, 2017 at 5:52 pm
Brandie Tarvin - Friday, November 10, 2017 5:49 AMSean Lange - Thursday, November 9, 2017 2:42 PMdrew.allen - Thursday, November 9, 2017 1:58 PMSo we had a problem updating a record in our third party product. I opened a case on the vendor's website and detailed the steps that I took to create the problem. There was a recent job change and the incorrect hours per pay period were entered in the form for the job change. The steps included correcting the most recent history record to fix the hours per pay period and entering the final annual salary so that the interface would calculate the correct hourly, weekly, and pay period salaries. When the tech assigned to the case tried to recreate the problem, she added a new job history record instead of updating the most recent job history record and entered the hourly rate instead of the annual salary as the basis for calculating the other fields. She was unable to recreate the issue. Is it any surprise, since she couldn't even follow the steps to recreate the issue? :angry:Drew
Sounds like most people in technical support I deal with regularly. They are in support because they can't pay attention to detail well enough to make it as a developer. 🙂
When we were hiring for our contract job, we specified "attention to details" as a must. Then we got candidates who made comments like "oh, but my skills are to focus on the high level stuff, not the little things" when we started asking technical questions on the phone interviews.
Needless to say, none of them made it past that stage.
Heh... I've been through similar... Sr. DBA candidates that complain to their "handlers" that I ask too many questions about SQL Server.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 10, 2017 at 7:28 pm
Sean Lange - Thursday, November 9, 2017 2:42 PMSounds like most people in technical support I deal with regularly. They are in support because they can't pay attention to detail well enough to make it as a developer. 🙂
A few decades back, a lot of technical support was competent. The cause was quite simple: developers were expected to do some technical support work as well as development. Then came this strange new attitude from across the pond that said the the developers were the real engineers and technical support was for weak also-rans. So developers in the UK would refuse to do any technical support work, emulating the insance American system. So almsot everybody decided that doing technical support was beneath their dignity, a management attitude that said these people doing this menial technical support stuff didn't deserve decent pay and benefits, and certainly were not worth much training (and as they weren't paid enough to buy their own training the results should be pretty obvious). The software business would have a dar better reputation if companies insisted that developers do stints in technical support, and technical support people do stints in development, but it won't happen while competent engineers both disparage technical support people and claim that doing technical support is not a fit task for real engineers.
I managed - mostly by luck, I guess - never to be involved with development of any products for which the developers didn't do techncal support, so I was never associated with a company whose technical support was useless rubbish. At Neos we went a lot further than that - if customers reported bugs there was a straight-forward escalation procedure (written into the contracts with our customers) which ensured that anything serious meant the customer would have the personal attention of the CEO if there wasn't a working fix to the costomer's systems within 36 hours and that wasn't way back in the good old days, it was in the 2000s. I was for quite a long time the step below the CEO in that contractual esclation procedure (and for a shorter time was at the top level as acting but unofficial CEO) and was occassionally (but rarely - our stuff rarely had serious problems) woken in the small hours of the morning by calls from unhappy customers, so I know the customers took that part of the contract seriously.
Tom
Viewing 15 posts - 60,346 through 60,360 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply