Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Client: There is a high severity production issue.. you need to fix urgently..
Developer: I am on the way.. Will fix it once I reach home.
Client: I don't care where you are. Fix it right now😡😡
Developer
14 -
”Are you planning on having kids in the near future?”
Literally (very) illegal to ask where I live. Too bad I was too young to understand the severity of him asking.
Worst place I’ve ever worked.8 -
Client: There is a high severity production issue.. you need to fix urgently..
Developer: I am on the way.. Will fix it once I reach home.
Client: I don't care where you are. Fix it right now😡😡
See the developer!!!
3 -
No other language can do something as fucky as javascript.
"7 high severity vulnerabilities"
$> npm audit fix --force
"13 vulnerabilities (11 high, 2 critical)"
How is this fixed?!
It will be a great day when JS finally prolapses under the weight of its own hubris.11 -
1. high severity production incident was asked to look into at the end of the day.
2. needed fix in ui.
3. fixed and deployed in 1 hour.
4. issue remained. debugging began.
5. gave up at 1 AM and went to sleep.
6. woke up at 6 and after debugging for 2 hours, identified to be a back end issue.
7. worked with back end team for the fix, and 6 hours and 3 deployments later, it worked.
8. third party vendor reported they are still not receiving one parameter from us.
9. back end team realised they forgot to ask ui to send another parameter.
10. added the parameter in ui, redeployed ui.
11. build and deployment tool broke down. got it fixed. delay of 1.5 hours.
12. finally things are in place. total time 26 hours.
13. found half bottle of vodka, leftover from last weekend. *Priceless*1 -
Only touching the topic slightly:
In my school time we had a windows domain where everyone would login to on every computer. You also had a small private storage accessible as network share that would be mapped to a drive letter so everyone could find it. The whole folder containing the private subfolders of everyone was shared so you could see all names but they were only accessible to the owner.
At some point, though, I tried opening them again but this time I could see the contents. That was quite unexpected so I tried reading some generic file which also worked without problems. Even the write command went through successfully. Beginning to grasp the severity of the misconfiguration I verified with other userfolders and even borrowed the account of someone else.
Skipping the "report a problem" form, which would have been read at at least in the next couple hours but I figured this was too serious, I went straight to the admin and told him what I found. You can't believe how quickly he ran off to the admin room to have a look/fix the permissions. -
our tester arguing with software house about blocker severity bug
SH: "No, this bug is not possible. It's possible only when you are logged as admin in other tab"
T: "I managed to replicate it in another browser in private mode"
SH: "But you can't replicate the bug now"
T: "True that I don't know steps to replicate it and it occurs just sometimes... Let me check right now"
...
T: "Okay, I managed to replicate it right now in private mode in other browser on normal user account"
SH: "Because you are admin"
They are pretending to be idiots or just are?6 -
So I decided to positively tackle the negative energy surrounding me these past few days. I tried to be productive. I went overboard, of course. Where is the fun in normal?
I wrote down all the urgent tasks I must die-die finish. Anyone closed with Asians will know the severity of the die-die and must combo. I started with tasks I have to finish in 3 days. Then in a week. Then in 2 weeks. I ended up creating more than 25 cards across my respective Trello boards.
The tasks that come to me always need minimum 3,4 working hours. Literally. The furthest deadline I see is Oct 15. The tasks I counted is more than 25. No appointments nor meetings were counted yet. It is not impossible. If I finish 2 tasks per day, 14 days is enough to complete all. I might have to continuously work 2 whole weeks of course. But it is still fine, right? Right, guys? Right? It's doable. Right?
I won't get any unskippable appointment within this 2 weeks. Right?
I won't get new tasks to finish within this 2 weeks. Right?
I won't have to guide other people how to do their tasks within this 2 weeks. Right?
I won't have to work other people's tasks when they absent within this 2 weeks. Right?
I won't have to entertain any annoying client because customer service team can't deal within this 2 weeks. Right?
I won't have to do other personal tasks within this 2 weeks. Right? (Like helping with creating a wedding slideshow for a friend marrying on Oct 28)
My life is totally fine. Right?3 -
Sorry, long since my last post...
I have quit my job recently at DERP & CO.. The level of anxiety was already somewhat of medical severity.
For months I had been in a project that not only did not progress, but that it was getting worst day by day.
A bit of Context
November: "Dev, junior anon needs you to help him on the SHIT project because they are running out of time, it is mainly doing unit tests."
Well, the code was a mess, there was a LOT of copy paste and it was all bad quality (we talk about methods with complexities between 80 and 120 according to SONAR QUBE).
Dev: "Anon, you know this is wrong, right?"
Anon: "Why? it works"
Dev: after long explanation.
Anon: "Oh well, yes, from now on I will take it into account." And he did it / try his best.
Dev does the unit tests and do extra work outside of the reach of the sprint (y than i mean work after hours, classic) and alerts the boss of the mess.
December: After a project of approximately 6 or 8 months of development, the boss discovers that the junior anon have been doing everything wrong and/or with poor quality (indicating that throughout the whole development the quality of the code was NEVER checked nor the functionality).
Boss: "This is a shit. Dev, you have to correct all the errors and warnings marked on sonar", which are around 1200 between smelling code, high risk errors, etc.
Dev fixes something like 900 bugs... lots of hours...
Boss: "This still is all wrong, we have to redo it. We will correct the errors leaving something stable and we will make a new repository with everything programmed as it should be, with quality and all"
- 900 corrections later, now are irrelevant -
Boss: "Dev, you will start to redo it, anon is out on other project. First you must leave the existing one working properly"
Dev: "ok ..."
January: How can I correct the mess if the client asks for more things. I am just fixing the mess, doing new functionalities, and when I have free time (outside the work) I try to advance the new repository, poorly I must say because burntout.
Boss: "Everything should be arranged at the end of January, so that you can redo everything well in February."
I can't handle everything, it starts to fall further behind. Junior Anon quits the job.
February: Big Bad Bugs in the code appear and practically monopolize the month (the code is very coupled with itself and touching in one place sometimes meant breaking other stuff).
Boss: "It can't be, you've been with this since January and you haven't even started correcting this mess in the new repo"
Dev: "It is that between the new things that are requested and the bugs I cannot put myself with that"
Boss: "Do not worry, you will be helped by random dev if you needed. SPOILER ALERT: random dev is allways bussy. Not made up bussy, He had a lot of work by itself, but it can't help me the way I need it.
High anxiety levels, using free time to try to reduce the work left and gradually losing the taste for develop.
March: So far, not only do they add new things day and day, but now they want to modify things that were already "ok", add new ones and refactor everything in a new repo. I just did not see an end of this nonsense.
Dev breaks, the doctor says it's anxiety, so I just know what I have to do.
Dev: "I quit my job"
Cool Manager: "Damn, why?"
Explain everithig
Cool Manager: "Do you want to try if I can change you to other project or anotjer scope on the same project?"
Dev: "Thanks, but no Thanks. I need to stop for a while".
End. sry for long sad post and maybe poor use of English (?) Not my native language.10 -
jQuery < 3.4.0 is a known moderate severity vulnerability now and Github just send me about 20 alert mails for repos which are using jQuery that I had used for side projects.
Like thanks but damn.2 -
So, my company pays thousands and thousands of euros just to show map and enable geocoding, a bug in google maps prevent Google Maps to work in Cordova and it's blocking us from deploying. After days and days of research I understand I can't solve it and I open an issue on google platform. Result: Severity -> S4, Priority -> P43
-
>makes a bug report about the JS linter in Eclipse Che not working
> makes it a P2 bug (moderate severity)
> confirms in their current implementation it doesnt work
> escalates to P1 (high severity)
wow for once Eclipse is actually making their shit better -
Fucked up.
Reviewed a code and gave ship it for a colleague's code change.
In a single day, got high severity ticket cut to the team.
I am done. Not going to do anymore code reviews. I suck at it.3 -
I'm Programmer/Analyst in one of the hgh ranking BPO company here at Philippines.
I'm currently on a project, I'm on a team who's managing machines parts. The project is CATERPILLAR.
The biggest challenge here is if there is a outage on the system, the number of Severity 1 issues keeps coming like there's no tomorrow. And there's only 5 of us on Tier 2 which is managing this abends, errors, bugs in the system.
Is there a way on preventing this outage/connection error. Like HELLO IT IS A BIG COMPANY !!! HOW THE HELL THEY CAN'T EVEN MANAGE THEIR CONNECTION!!!!2 -
So the project I work on basically has to talk to a 3rd party plugin, through a 3rd party framework. The 3rd party plugin is a black box. This conversation happened:
Software guy: so we aren't sure what is breaking the thing. It's either us or the plugin, but it's probably both.
Systems guy: well then if we aren't sure then why are we writing an issue for it.
SWG: because we aren't sure but we know we are doing at least something that contributes. We read int X from a table and put it into a float. X doesn't perfectly represent in a float. It comes out X.0001. Then they take it and when it comes back it comes back as Y.0001. We cram it into an int so it becomes Y, we compare it to X which is really X.0001 and it comes back invalid.
SG: well as long as we are sending them the right number . . .
SWG: but we aren't sending them the right number. They are expecting X not X.0001. Then they send us back Y.0001 but it should be X so it's wrong.
SG: so they're giving us the wrong return value.
SWG: yes, but because we're giving them the wrong number.
SG: well not exactly . . .
SWG: yes exactly. It is off by .0001 because of floating point math.
SG: well . . .
Me: look it doesn't matter how it's breaking. But it IS broken. Which is why we're filling out the damn problem report. THEY ARE EDITABLE. We talked to the customer and gave them the risk assessment. They don't care. It happens rarely any way.
SG: then can we lower the severity?
Me: no. Severity doesn't relate to risk. That is a whole different process. Severity assumes it has already happened. It's a a high severity.
SG: but the metrics.
Me: WE GIVE THE METRICS TO THE CUSTOMER. WE TALKED TO THE CUSTOMER. THEY DON'T GIVE A SHIT.
And that was how I spent Wednesday wondering how a level 4 lead systems engineer got his job. How many push ups did he do? What kind of juice did he drink?2 -
Fuck these frequent "URGENT TO REVIEW" pull requests with 10+ files changed by lead each time, amirite or amirite?1
-
So I have two bugs to fix, their severity don't make sense to me
One is classed Medium while it's just some changes in design and ergonomy
One is classed Low while it's a functionnality that is not working
Priorities ¯\_(ツ)_/¯3 -
My manager, while apparently trying to blast us over taking too much time to understand a product (that no one in the team knows about completely):
I don't understand why you guys don't understand the severity of it. How will you support the product if you don't even know it? There's no comments or anything also, just code! You guys should be able to grasp it!
I'm sorry, what now?
(The part about no comments is true, by the way) -
The first company I worked for had a policy to not ship any release, service pack or hot fix as long as there were still open bugs with the severity "critical" or "blocker". They wanted to ship a service pack nonetheless, but without violating the rule and thus keeping their KPI unharmed. So the support guys got in touch with developers and asked them to lower the severity of certain "critical" bugs. They said we by all means need to write into the comments that the severity of those bugs has to be reset after the service pack was shipped, so that those important bugs would not be left behind.
- Support team violates the rules set up by themselves.
- Developers had the actual work of doing so (and the blame to catch).
- The Support team's KPI just remained unharmed.1 -
So if you recall, my last rant was about last minute, supposed critical-severity, ASAP due date requests being made, and me telling them to fuck off.
So today the boss' boss' boss called down and said a different task needs to be done by end of the month.
So now my current tasks get pushed to next month, and the person who needed their task done ASAP will now more than likely get it by mid june. Amazing.
And if you've been actively following my other rants, this is the same section manager that sends a quirky email out at the end of every night about what she's been fucking with lately.
I WANT OFF MR TOAD'S WILD RIDE -
Y'know, there are some things that are timeless. Like bug severity arguments. We don't have a "likeliness of occurrence" parameter in the bug database. We just have "severity if it occurs". You have to classify it as such. The bug database IS NOT FOR RISK MITIGATION ACTIVITIES IT'S FOR FIXING THE FUCKING SOFTWARE!!! STOP MAKING THESE DAMN MEETINGS TAKE 30 YEARS BY QUESTIONING THE SYSTEM THAT WAS ESTABLISHED IN THE BEFORE TIMES BY PEOPLE WHO ARE ABOVE YOUR PAY GRADE!!! TINDER BOX!!! MATCH!!! GODS DAMMIT!!!
-
Severity 1 issue on the company today... No back ends for the full country... It was even exciting, don't aak why.
-
Did someone already thought about how color highlight can be better? It's been 4-5 years now that I'm coding on a virtual console that run on iPad with a monochrome code editor. Despite the fact that's remind me the old days when I was 8 years old, that doesn't stop me for coding with it.
I mean, is it really important to know that strings are red and numbers are yellow? How does that help me? They are both literal and behave to the user-content categories.
I was talking with my friend, and he says he likes to know if something is a keyword or an identifier. In C++, a lot of common keywords to define stuff and control the flow are often the first word and easy to spot.
A couple of months ago, I tried Flutter, and the editor can highlight ident blocks and give them different colors, but with Flutter, it's easy to get 10 or more ident levels, Does the color help? Splitting the code does.
I think, there is so much stuff that is more important than coloring the grammar of a language. For instance: knowing if an identifier belongs to which Rust Crate because, It's easy to stack 10 or more dependencies in one file that as better chances of names collisions.
Knowing if an identifier was recognized, if it used, if it's a local, a member, a global, a compiled value or a macro seems more important.
I would like to color block of code that is important or sensible. That will help my coworker about the severity of a particular place in the code.
What do you think?1 -
You know what I noticed about a lot of people is that they just can't abide when people make them uncomfortable or work off their natural guilt impulses to not do things they shouldn't do, so they can be happy content fucking monsters.
really bothers them when you point out that they are in fact fucking monsters and no amount of warping the next or youngest generation into accepting horrific abuse or writing it off as a small thing, makes it so.
it's like what is in fact the worst thing that can happen prior to reaching the point of brain damage and severed limbs is not so much reduced in severity from the perspective of their brainwashed underclass, but downplayed to the point where it is just endured, and then later replicated.
thick glass wearing fucked up monsters !19
Top Tags
Weekly Rant
View