Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
bioDan536510dNice rant frank.
Its true, there are many dense developers inour community.
groxx24710dI particularly enjoy when they head to SO for a solution, and learn that e.g. Java doesn't have multiple returns or pointers. But you can do This One Weird Trick, and pass in an array of object, and mutate it to "return" more stuff. And then proceed to use it everywhere.
Or really just any time people shove stuff into base-object types to "work around a compiler limitation/bug".
inaba513710d> UP THE SINGLE-RESPONSIBILITY PATTERN JUST BECAUSE THE COMPILER SAYS YOU SHOULD
Now that just seems like something ~the compiler~ wouldn't do
Means : Your implementation was bad.
"Working around compiler bugs" with un-typed wrappers though... Yeah, that's pretty widespread. Thankfully not in my team tho.
@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
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job