@ObiWayneKenobi said:
@bridget99 said:CSliderCtrl::SetBuddy()
I'm not your buddy, friend!
Who you calling friend, pal?
@ObiWayneKenobi said:
@bridget99 said:CSliderCtrl::SetBuddy()
I'm not your buddy, friend!
Who you calling friend, pal?
I can't believe I haven't seen the classic passive-aggressive option here.
Mutter to yourself as you work. Honestly, it seems difficult at first but once you get going it's self-sustaining. Muttering is enough to keep away some of the timid.
Whenever someone tries to interrupt you hold up your INDEX finger in the classic "hold a moment" gesture. Then go back to what you were doing and muttering. Ignore the person completely. If they make any noise, repeat the "hold a moment" gesture. Repeat until they go away.
Eventually they'll realizing that trying to bother you gets no result and will go bother someone else. It takes a little more time but it's quite effective and gets more of a "he's too busy to do that - go talk to [other person]" attitude going.
Note - make sure it isn't someone actually important trying to get your attention. That would be .. bad.
Unless you're being asked to write up all the missing parts of the documention then I too fail to see the WTF in this. You're charged with doing the deployment, document the damn thing as you've been told to do.
Wow? Someone else to clean up all my warnings? How do I sign up for this??
I stupidly spend all the time at the end of a project clearing up warnings and adding annotation.
@belgariontheking said:
My next guess is different schema in DEV/QA versus PROD, but that would be too obvious.
Second that. I've been dealing with a DEV/QA vs PROD situation like that for years.
@campkev said:
TRWTF is that you have a credit card at all. Cut it up and cancel the account. I got out of the credit card game three years ago and life has been much better ever since
Try renting a car without a credit card. Ditto with reserving a hotel room. Buying an airline ticket is also kind of difficult.
If you have a debit card through your bank you generally have a credit card too. Look at the little logo in the corner. It isn't there just for decoration. If it's there, you have what amounts to a credit card even if the money is taken out of your account just like when you use a PIN.
Keeping a credit card for emergencies makes good sense. What are you going to do when your car needs $2,500 in repairs and you don't have the cash? Think about it.
This action actually has a name - "Threadomancy" and people who realize they're responding to a very old post will use it somehow.
I've seen it happen in a number of circumstances and about 75% of the time it actually is appropriate (trying to bring an outstanding issue to conclusion, saying thanks for a solution that actually worked, etc.) and the other 25% of the time is because someone was too lazy to see if there was a newer thread.
EDIT - ~facepalm~
Yeah, I just looked at the dates on the original posts. Um... threadomancy?
@Ren said:
@Nexzus said:
Format the document in excel to be printed at one page wide. Print the document. Scan-to-email (pdf image) the printed document to himself, Email that document to one of the admin staff, who would then: Enter each account manually from either the screen, or (usually) another printed copy.
What's wrong with [b]OCD[/b] ?
FTFY
@ComputerForumUser said:
I'm more bothered that some pages require javascript to work even though they behave identically to plain old html
OMFG. I'm cleaning up a club's web page in my copious spare time and the original developer has the e-mail addresses being generated by JS as the page is rendered. The output is identical to just putting the frappin' HTML in place.
My guess is that this is either some primitive attempt to spoof the address scrapers or he found the code somewhere and thought it was 'cool'.
Don't even get me started on the lame attempts at CSS.
<QUOTE>@ueberbill said:
I'm a salaried employee- my initial offer letter stated as much and I work and am paid like your average salaried employee.
Research the labor laws in your country/state. Find out their definition of 'salaried' and what's allowed.
If you find that your company is not complying with your country/state's legal definition of 'salaried' then send a copy of your offer letter and a well written memo explaining how their policy violates the law. Include the statement that you expect any vacation time that has been deducted to be replaced and a reply in writing stating either: they will no longer apply this company policy to you or that they do not consider you exempt from the policy. Make sure you put a reasonable deadline for their response. Lack of a response is as much of an answer as a reply.
If you get your vacation time back and the 'good' reply then file it away and be done.
If you don't get your vacation time back and the 'bad' reply OR if you get your past vacation time back and notified that all future events will result in deduction of your vacation time then take the entire packet to an employment lawyer. And start looking for another job and hope that company doesn't ignore labor laws.
@shepd said:
And this, my friends, is why most companies do worse when they get really big. They hire HR departments. The HR department employees have never started their own company, nor run one. The HR deparment believes that every qualification has a certain university degree/college diploma/high school education attached to it, and that is all that is looked at, because it's easy. Why would you want to hire the guy with the 35 year old degree in Physics and 30 years field experience as a programmer when you can get the not-yet-even-graduated 2nd year University student instead?
And this is why I refused to let HR filter any of the resumes that came in for open positions when I was a hiring manager. Sure, I would get a stack of them and about 90% ended up in the Rejected stack but I was able to make that determination. Several of the people I hired would never have made it past the HR department but were great employees. Because I was looking for things besides a laundry list of degrees/certs/etc. And you can't put that judgement call into an area that doesn't do the job.
BTW - I'm going to digress slightly here in hopes of helping other hiring managers who might read this site. Here's how I went about hiring new members of my teams.
Yes, this sounds like a bit more work but if you're hiring to add to a team then that team really should have some kind of say in the new person. If you happen to like someone who isn't going to mesh, then you're not adding to the team. HR was amazed both by the process and the quality of hires we got out of it. Next time you need to hire someone think about trying this, if practical.
Note 1 - Make sure you go over the interview basics with your team, as in what you can and can't ask.
@DOA said:
I guess "fixing" software is easier than fixing idiocy.
"Fixing" software really is easier than fixing idiocy. Of course, this will severely impact team productivity because I'm guessing that the 'Reply to All' function is used 98% of the time for good reason and 2% of the time by morons.
A better software fix would be to only disable it on specific clients. Like, those 2% who have been doing Reply to All on company communications.
But since it's probably the senior executives' admins who are doing it then it is more politically correct to remove the function for everyone rather than single out the offenders.
I love workforce noobs. I could snicker over them all day except that I'm getting on with whatever project/work assignment I was given.
And when the guy gets fired it's going to be because "They were intimidated by my level of knowledge and they knew I was right when they were wrong." or some similar whiny self-justifying excuse.
When you're hired to write code, you write code. You perform the task required. It is mostly boring and rarely offers a chance to do something really fun and elegant but that's how I pay the mortgage. I treasure the assignments that let me stretch and learn new things. But I know that I have to slog through the rest of it to get those. And because I take on whatever needs to be done and get it done with a minimum of fuss I'm considered a valued employee.
As I've told my boss with a complete straight face and perfect honesty: "I'm a tool. I'm a happy tool but a tool nonetheless." And I'm good with that. I'm a tool to get the job done. And not 'tool' in the derogatory way some people use it.
Bravo for trying to get him to understand that he needs to do what's in front of him. It won't work because he seems convinced of his own superiority but at least you tried.
Please let us know when he gets fired. Do you have a pool going on it yet?
They had a card that represented one glue stick of this exact inventory type. So instead of just doing 20 @ [scan] and getting 20 of them, we had to count out loud as each one scanned. And it didn't always 'take' on the scan so it wasn't a matter of running the card over the scanner 20 times.
As this was going on the line behind me was getting longer and longer and longer.
So while it might have seemed like a good idea up in some corner office it is in reality a horrible way to try to get customers through the check out process.
Sunstorm's concept of 'create an item to represent X of that item' makes no real sense since people can buy anything from 1 to 500. Trying to make cards for 5, 10, 20, etc. doesn't fix the underlying issue of 'we're going to make this as difficult as possible for the customers'.
I haven't written or called the home office yet because I've been busy with other things and the system is still pretty new so I'm thinking that this will be added in a very short time as they analyze the data.
I'm a craft-type person and therefore shop at .. wait for it .. craft-type stores. For the person who doesn't waste time, money and space on craft related items this means I buy things like 20 hot glue sticks for a US dollar when they're on sale.
The craft store having this sale currently has a new POS system. They're ringing up my intended purchase, which includes the aforementioned 20 hot glue sticks.
They find the card with the appropriate bar code. And proceed to scan it 20 times.
WTF?
I (politely) ask if they can't just use 20 @ [scan] (like they used to quantity 20 of item) and they nicely tell me that whoever designed their new system decided that every item has to be entered individually unless there's something like 50 of the item.
So we're both counting out loud as she scans the bar code card 20 times. Note, I watched the screen and it doesn't tell you how many you've done. Each one is a separate line item. I'd have to pull out my receipt to see if it summarized them or not. My thought is 'not'.
And to make things better, this was part of a weekend sale. None of them rang up at the sale price. So she has to void the sale and start over. THEN they rang up correctly. I thought this was a singular event but when I went to another store on the same day (I was looking for a very specific thing) it happened the exact same way - first time, no weekend sale. Cancel and re-scan, weekend sale.
Yeah, that's a well-designed system all right.
Welcome to The Real World
Most large companies don't use niche products nor do they support them. You'll notice that they worked just fine on a commonly used application.
Learn from that and you'll be just fine. Continue to insist that things work on what would be called 'hobbiest' applications in another age and you'll find it hard going.
My normal response when faced with a project like that is to present a first-pass requirements list off to my boss. In this case something like:
I think you get the idea.
Since your boss seems to think that this is easy (see appropriate Dilbert cartoon) then you're kinda screwed but at least you've documented what you need to make it work.