Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "urgent on friday"
Product: Hey, this screwdriver feature I never requested isn’t there. Why? Can you fix it? It’s kinda urgent.
Product: @Root please jump on the ticket above … fairly urgent.
Root: It’s Friday, I’m out next week, and I’m working on finishing <urgent comma ticket> right now.
Boss: Work on the screwdriver instead. But make sure you finish the comma ticket too!
Boss: By the way, I volunteered you for eight security reviews next month!
Security: You’re on call for AWS audits next month, too!11
A new urgent request today…
“ITS URGENT WE NEED THIS CODE IN IMMEDIATELY I DONT CARE IF ITS FRIDAY WE NEED IT THERE BY ONE HOUR”
“What is happening?”
“ADD THIS CODE TO OUR CODE”
(A snippet to track marketing conversions from fb)
“Uhhh it’s Friday and our product won’t release to the public for 2 months anyway?”
“YOU DONT GET HOW URGENT IT IS, MUST BE THERE IN AN HOUR OR WE’LL LOSE DATA”
Spoiler: data said that today we had no customers on an unreleased project. Go figure!5
3:30 on a Friday, random PM: our Argentina devs just sent out a merge request. We need to release before the weekend.
me: We try not to release on Friday afternoon unless it's for a high priority bug fix.
PM: This is urgent
PM: We're two weeks behind schedule and the dev for this it's going on vacation in an hour.
me: so, you want to release when there's no one around if something goes wrong and the person who knows anything about it isn't contactable?
BOSS/SUPPORT/CLIENT: IT’S URGENT!!!! IT’S URGENT!!!!
Me: if it was really urgent why are you asking me about it at 5’oclock on FRIDAY2
PM: stressed out and during the briefing, keep reminding us how urgent is this project:
"This project need to go live this Friday"
"We only have 5 days to complete this."
"Client need this campaign to go live as soon as possible"
"We need to have a quick catch up every morning to ensure we are on track"
I have been working in digital agency for 7 years. When you heard something like this, there's a high chance that the deadline is a FAKE deadline. Very likely it will be delayed for another few days.1
PM: Yes, so, could you please do those changes on this page tomorrow by 3 pm and push to prod?
Me: Yeah sure! Noted :) (task is to "untick" a checkbox in a page's settings on our CMS)
* the next day -- 11 am *
PM: erm yes so please can you do the changes I told you about, it's getting urgent and you didn't start it already and it stresses the hell out of me because today is friday and it needs to be up and running fine for Monday 12pm and you don't work on weekend so I'd like yo-
BOSS and Client IT’S URGENT IT’S CRITICAL
ME: IT’S 4:30pm on FRIDAY AND THIS IS THE FIRST I’VE HEARD OF IT IT IS NOT THAT HOT2
Attention: incomming resentful boiled up for months rant.
Hands down G2APAY is the worst because:
Merchant account aproval takes fcking months. It starts with unreasonable delays in documents approval. I mean insane nitpicking. They want to see merchants name surname and address on every god damn document that you submit even if for example bank statement doesnt include these details. I had to manually edit pdf’s just so that they would fck off and approve the merchant application. Insane requirements for document check also combined with their email only support answering only once a week you will have to wait one month just to get your account approved.
Then you get to the fun part, approval proccess for vendor gateway and webhook integration. They are nitpicking everything you can imagine: about website not having https, website forum missing some icons, merchants phone number being from another country then he is, and bunch of other hundreds of problems imagined only by them. Again combined with their one email reply per week policy you will waste atleast one month to finish up your integration.
Now finally you are their client and you think you can chill and go back to focusing on your business? Nope bro. Prepare for threatening emails. Last time I got a request to install https or my merchant application will be shut down. I was given 3 days notice on a fcking friday and had to do it.
Then g2a backend is crashing quite often. Combined with their one email per week policy you are fcked in the ass if your users were not able to pay through g2a and you will get no compensation.
Their backend documentation is shiet. Not clear how to integrate everything and after you integrate they make changes without publishing any changesets. Your integration is working? Good luck if it will still be working tomorrow.
And the very worst part is that they stopped proccessing credit cards like month ago with zero notice. Its been weeks and still zero news about bringing card proccessing back. They sad that they were acquired by some other company so shitty support got even shittier now while they are in a proccess of handover.
So yeah thats the worst vendor I have ever seen in my life. For example integrating paypal took me 30 minutes. Integrating stripe and getting all documents reviewed took me one business day. Same with paymentwall integration and document approval took 1 business day. Support is amazing and even have a phone number that I can reach if urgent problems arise. Thats how it should be. Thats why I can pay percentage of my transactions with a smile for them.
Sorry for the typos since im typing on my shiet phone while driving.
Eat a bag of dicks g2apay. I hope you go bankrupt and shutdown.21
Friday afternoon, the week's work is finished, and I'm ahead of schedule.
An email arrives for another project.. "URGENT yaddayadda". The dickheads where it came from have taken weeks to react, and now it's urgent. Yeah, fuck you assholes, ideally with a smoothing iron.
On the upside, I'm not addressed directly, and that project isn't my task. But boss could make it mine in no time, and I think he would.
I don't even open the email, nobody has seen it anyway yet, AND I GO HOME! :-)3
The moment when your teammate raises a 150+ file pull request on Friday evening and marks it as urgent.1
Fuck those customers...
Wednesday: Sprint Planning
Customer: We want those two datepickers in the job application form to be text fields instead
Me: Okay, this will take some time bc I have to change the data structure too.
Customer: Okay do that. this is urgent
Thursday: implemented and merged
Monday: QS approved it
Yesterday (Tuesday) in the morning:
Customer (via Slack as a PN): Hey! Why are those fields no datepickers anymore? We want to show that to our boss this Friday! And why do we have this small icon on the right side of the field (Chromes autocompletion)
Me (to PM): Could you please tell them to think before creating tickets or writing some shit?2
TLDR: coworkers are worst than clients on delivery
The endless script last part, or where I want to rip the vocal chords out of my coworker’s throat.
Delivered “quickly” last Friday night as he was stressing me, because it was urgent, because he started shit I had to refactor, because I have better shit to get done.
It’s also important to note that this “senior” sysadmin wrote requirements as follows : told me orally what he needed between a gasp and another and drew me something that looked like a diagram but without real sense. I told myself -Well, let’s get this pile of cow shit together.
Anyway, it required some amount of time to put his giant shit mix of powershell and batch together, also it was quickly but it was tested and it worked on different conditions that I specifically wrote out and designed to have menus where you can’t do shit (like putting a string on a number input).
Today he comes to me and asked if it was ready and I told him it was usable. He tries it, doesn’t know how to use it, abandons it. Then he tells me he doesn’t work how “required” and after 5 Minutes on telling Shit I tested on the exact same server, he said “well my version was ok but you know I could have been more precise”
YOU INORGANIC PILE OF PIGEON SHIT. THE FUCKING SCRIPT IS WORKING, IS REFACTORED AS IT SHOULD AND YOU DON’T UNDERSTAND A CRAP ABOUT THE FUCK YOU’RE EXECUTING.
Seriously, come tell me that you can’t see what happens. I did explicit every fucking command out for you, I even bothered to put fucking Write-Host everywhere with Colors just for your fucking sake taste.
Go fuck a pillow with your biker sunglasses.
And no, the way you cut your beard doesn’t make me think you’re 15 years younger, it makes me think you’re the kind of guy I would not accept candies outside a school.
P.s.: don’t accept candies even if the guy looks nice.1
I went into interview last Friday and felt great. The recruiter said they needed people urgent, so I'll be hearing from him soon. On Monday he called me saying they liked me and would like me to join the team, so he will prepare a proposal for me.
It's been three days and I haven't received any information or contact with him about the proposal.
How much did it usually takes to create a contract proposal?
I was thinking about the problems one of our clients faced with the launch of their project the other day, because things were rushed, stuff was omitted and in the end they could not meet the launch date, and I started making a list of hard lessons I learned over the years that would have helped them avoid this situation.
Feel free to add yours in the comments.
- Never deploy on Friday
- Never make infrastructure changes right before a launch
- Always have backups. Always!
- Version control is never optional
- A missed deadline is better than a failed launch
- If everything is urgent, nothing is important
- Fast and cheap, cheap and quality, quality and fast. Only one pair at a time can be achieved
- Never rush the start or the end of a project
- Stability is always better that speed
- Make technical decisions based on the needs of the project two years from now
- Code like you will be the only maintainor of the project two years from now. You probably will...
- Always test before you deploy
- You can never have too many backups (see above)
- Code without documentation is a tool without instructions
- Free or famous does not necessarily mean useful or good
- If you need multiple sentences to explain a method, you should probably refactor
- If your logic is checked beforehand, writing the code becomes way easier
- Never assume you understand a request the first time around. Always follow up and confirm
There are many more that should be on this list, but this is what came to mind now.2