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
-
@bioDan i was gonna do that joke! I am disappointed!!!
-
@inaba he was making three entire classes and interfaces async because one method required it
-
@groxx Sometimes it’s just people thinking “Yeas, I’m sure I need to do that”.
I have a recent example, of myself. I needed to make a fire and forget code (Basically send an HTPS request and not caring about return value).
C#. I did “async Tasks MyMethod bla(params)”
Well, when I called it without await keyword : Compilator warning “Not awaited”. First reaction : Well, I know, I don’t want to await that !
Fix was easy. “async void MyMethod bla(params)”
Made compilator happy and represented better the function. So some times it’s just a “syntax” issue -
@alexbrooklyn how do you make a class and an interface async tho? 🤔
Lemme be frank for a moment
Just because the compiler tells you that you need to do a certain thing, DOESN'T MEAN YOU SHOULD SEE THAT AS THE ONLY FUCKING SOLUTION
DON'T START FUCKING UP THE SINGLE-RESPONSIBILITY PATTERN JUST BECAUSE THE COMPILER SAYS YOU SHOULD, HOW DENSE MUST YOU BE TO THINK THAT'S THE FUCKING SOLUTION?! PERHAPS YOU SHOULD DIG A LITTLE BIT DEEPER? I CAN'T EVEN LAUGH ABOUT IT IT'S SO SAD. DEADLINE IS GETTING CLOSER DAMNIT
Oh btw, another instance:
"I'm doing X to achieve Y because I'm more familiar with step 1 of X"
Fine, but that takes more time and can be done in way Z, in that way, you don't loose precious time and can just work on the other steps in the proces that contineously get harder.
* Person proceeds to do X anyway and get stuck, in the end having nothing done *
🙄
I like helping people, I really do
But I'm not going to loosen the knot around your neck if you keep tightening it
rant