New and Unimproved Workplace Rants

There is a tiny town about 5 miles away that has a drive through for buying MJ.

New bills tend to stick together, maybe they are used to getting new bills? I agree it is a disgusting habit. Not to mention 92% of US bills test positive for cocaine, dont want to think what else there may be on there.

Hmm, might have to try this bill-licking thing…

So, about two months ago, one project I worked on ended, and a follow-on project started. I had completed a nice code base and was ready to continue with it. But not so fast! There are contractual obligations; you can’t just use code from one project on another project.

Here are the hoops that had to be jumped through.

  1. I make a request to use the code on the new project.
  2. My program manager makes formal request to receive the code.
  3. Request goes to my Company’s contracts office.
  4. My contracts office approves and sends request to receive code to Prime Contractor contracts office.
  5. Prime contracts office sends to Prime’s program manager for approval.
  6. Prime’s program manager sends approval back to their contracts office.
  7. Prime’s contracts office approves and sends request to Customer’s contracts office.
  8. Customer’s contracts office sends request to Customer’s program manager for approval.
  9. Customer’s program manager asks for confirmation from previous program manager.
  10. Previous manager approves.
  11. Current program manager sends approval to receive the code to their contracts office.
  12. Then, Customer’s contracts office sends request to deliver code to Prime Contractor.
  13. Prime Contractor contracts office sends request to deliver code to my Company.
  14. My Company’s contract’s office sends request to deliver code to my program manager.
  15. My program managers asks if it’s okay to deliver the code to the project.
  16. Hmm, should I give myself permission to use the code I wrote? After due diligence, I deem myself worthy.
  17. My program manager relays approval to deliver code my Company’s contracts office.
  18. My Company’s contracts office gives approval to Prime’s contracts office.
  19. Prime’s contracts office sends delivery approval to Customer’s contracts office.
  20. Customer’s contracts office forwards approval to Prime’s contract office.
  21. Prime’s contracts office realizes the email chain has Prime’s proprietary information comingled in it. Try again!
  22. Repeating previous steps 5 through 11 (or something like, this part is opaque to me).
  23. Prime’s contracts office forwards approval to my Company’s contract office.
  24. My Company’s contracts office sends approval to delivery code to my program manager.
  25. My program manager says: you’re good to go.
  26. I email myself my code, cc’ing contracts and others, as the official hand-off of the code.
  27. I can finally work on my code again.

Whee! The basic idea is sound: if the code were from another Prime Contractor, it makes sense I’d need their permission to use their code. It’s just weird that they jump through the same hoops even when one is “delivering” code to oneself.

Who in the almighty fuck thinks it’s a good idea to drop nearly a hundred pages of test results on someone’s desk, along with a list of non-conformances, at 4:45 PM on a Friday??? :rage: This person knows I’ll be working from home next week, and we’re not allowed to take the hard copies out of the building, so I had to stay and scan everything.

So, you’re working from home, but you can’t take your work home?

Or do they think it’s a security issue? In which case, do they realize you could accomplish the same industrial espionage with scans on your thumb drive?

They did scan them. I assume it’s more of a chain of custody thing. Can’t chance losing the originals, so they stay in the building.

Okay, that makes more sense.

But there should be a rule: If you’re dumping stuff on someone who’s working from home, you need to give them (legible) scans, not a stack of originals.

Yep, that’s it. Also, when management finds out there’s a problem (I don’t know exactly how big the problem is, since I didn’t really read through the reports), they will want to have a look at the results for themselves, which is much easier if the reports are left on the table where the other problem jobs and reports are kept.

Yes!!! I’m still not sure what this person gained by dumping all on my desk so late in the afternoon; they had to know that I wouldn’t look at it until Monday anyway.

Wonderful - our weekly stand up has just been highjacked by two people who are blissfully unburdened by doubt yelling past each other. The worst thing is that they are both saying the exact same fucking thing.

Something has happened that has caused the corporate office to send out mandatory anti-discrimination/inclusion training. (Og knows we could use it, but the problems run so deep that a single online class won’t begin to take care of it…that’s for another thread though.) Extremely detailed instructions for viewing the course were included with the email; in particular, the email noted that the course is meant to be viewed with CHROME (their emphasis), that certain content wouldn’t work outside of CHROME, and that you should contact the IT department if you had difficulty installing CHROME on your computer. Ok.

About five minutes later, our resident HR rep emailed the entire company to inform us that “fyi, you need to use the Chrome browser for this.” :expressionless:

… and five minutes before the training, fifteen people will ask “What is Chrome? Do I download it from the Apple store?”.

:grin:

I’m convinced at this point that the only reason my company hasn’t upgraded to Windows 10 is that the IT guy remembers the literal wailing that happened when we upgraded from Windows XP to 7.

So that Monday at 9:05 am, they can whine to somebody “But I gave it to him last week! What’s taking him so long?”

This pretty much happened, because an unrelated urgent matter popped up Monday morning, and I didn’t look at the results until Tuesday. By the time I sent out the questionable stuff for review, management had gotten involved.

Yep. Watch out. This person is a devious asshole, and did this on purpose. It’s hard for most of us to conceive that someone could be this nasty and plan this out… but they are out there.

I worked a couple hours on a report this morning, figured I’d be able to knock out a dozen case reviews.
Nope.
I spent 30 minutes alone on one case, trying to untangle all the issues. Missing court orders. Inappropriate actions taken. Unclear information.
Two more cases, same worker, a bunch of court orders were either not entered or entered incorrectly.
Then I spent another 5 minutes removing “ya moron” and fixing my emails so they wouldn’t be taken as attacks.
Which, I know they will anyways.

As annoying as all of that was, I can see the valid logic behind it in the event that ownership of one project and its resources go one way and ownership of the second project and resources go to a different entity.

That’s the kind of scenario that IP lawyers salivate over with thousands of billable hours.

Many of the documents here at work need to be stamped for a variety of reasons – being issued to another department, or being sent to a vendor for information, or even being marked up to assist inspectors. Acrobat’s stamp tool has always worked great for this; you can even add a bit of code so that the date (as in “date issued”) is automatically updated. Our document control department, however, has always relied on copying the stamps they need from an existing file on the server, then manually updating the text as needed.

Acrobat Pro DC made this feature a bit more accessible, so when the upgrade finally reached document control, I showed them how easy it would be to create a set of custom stamps within the program. Naturally, I was brushed off as a know-it-all engineer, too eager to interfere with something that worked perfectly well… That is, until this morning, when document control discovered that the file is now corrupt. There is much screaming.

I could show them how to check for previous versions of the file, but I guess I shouldn’t interfere.

Reviewing resumes for an open position in another department. Tedious, especially since the job is for a position I am not completely familiar with, but that is by design. I can deal with it. But a few things stand out:

  1. The job calls for being skilled in MS Office products, so it is appropriate to say you are proficient in Word, Outlook, Excel, and perhaps, if your current job really sucks, Power Point. But do not say Access. You don’t use Access. Yes, it’s on your machine. No, you don’t use it. Nobody does in this line of work.

  2. When describing your computer skills, if you use the terms ‘microcomputer’ and ‘CRT’, it’s time to either update the resume or retire. Probably retire.

  3. We expect that a good resume should include the requirements that are in the job announcement. If the announcement says skills A and B are required, then it is smart to write in the resume how your work experience relates to A and B. If you simply say “I know A and B”, then we know you are lazy and probably less than an ideal candidate. But if you cut and paste the exact words about A and B from the job announcement into your resume, with no other supporting verbage, then we know you are a stupid plagiarizing git. Do you think we don’t recognize the words that are in the job announcement?