Meme Monday!
Today's cover image comes from last week's thread.
DEV is an inclusive space! Humor in poor taste will be downvoted by mods.
Meme Monday!
Today's cover image comes from last week's thread.
DEV is an inclusive space! Humor in poor taste will be downvoted by mods.
For further actions, you may consider blocking this person and/or reporting abuse
Valery Zinchenko -
Ben Sinclair -
𒎏Wii 🏳️⚧️ -
Kathryn Grayson Nanz -
Top comments (63)
🙄
Happens to me too much...
I don't know enough about NPM but I often see this same problem.
and the additionally weird thing is that when I run
npm audit fix
a second time then it reverts to the other vulnerability list, then I run it again and it switches back to the 2nd message with a different number of vulnerabilities. I don't understand it, so I just do "hopeful" programming. Move on and hope it's not so bad.For me it usually happens something like this:
New project with 6 errors:
npm audit fix
: 20 new errors appear"A fix is available via 'npm audit fix --force'"
npm audit fix --force
: There are only 9 errors now(I proceed to give up and hope everything will be fine).
😃
I always wonder, if
npm audit fix
fixes the problem, why can't they run it themselves on the npm servers?It's an automated process that upgrades or downgrades the dependencies with vulnerabilities, which means it won't always fix the problem. I'ts often a 'breaking change' for small issues, which is not something you want to do globally.
Yes.
Let's kick it off with an awful AI-generated meme
He grew a beard in 72 hours?!
Looks like he lost his eyebrows as well...
that's how it works with me
Wow 😲
He was using an llm to bug fix and it advised him to cut his eyebrows off and glue them to his chin.
😂 I wonder how many people would actually do what it said (maybe for something less drastic)... some people trust AI too much...
We don’t know how stress can impact different people. 🤣
😆
Yes, out of stress.
😂
When it works(it shouldn't):-
Why is it working(even worse)
So true 😂
How a C developer writes Python code 😂
Don't be silly... a C developer would never write python code.
They always do but with semicolons 😂
Can confirm. As a python dev that's the most readable C I've ever seen.
Except the private static void is making me think it's Java 🤔 ⁉️
Java written by a lisp developer 😬
That's the most sensible explanation for vim I've ever heard. 10/5
As a python dev I do crash my car when handling webstyling. I do it on purpose though as it's easier than reading my own CSS.
Okay. I finally get memes. I guess I just had to relate!
laughs in vim
...What? A palindrome is "a word, verse, or sentence, that is the same when read backward or forward" like "racecar" and the name "Otto". So "()()" is absolutely a palindrome because backwards it is still "()()". The string "())(" backwards is ")(()", which is not the same string... Am I missing something??
"()()" backwards is ")()(" (open close open close backwards is close open close open), you are switching the open and close parentheses when you reverse it, which you wouldn't do in a palinfrome
That is more "inverting" than it is "reversing", as well the meme explicitly referred to it as a string (and when you reverse a string there's no additional operation of attempting you "invert" the characters, you just reorder the array of characters in the inverted direction).
Now I'm curious what a name of the operation for reversing and inverting characters would be to make this make more sense.
Inverting "()()" would make "()()", reversing is, split the string into individual characters, reverse the order of the list and join it back together. If a palindrome required inverting, then "racecar" wouldn't be a palindrome because "ɿɒɔɘɔɒɿ" is not the same as "racecar". "()()" doesn't read the same backwards as forwards because forwards it is "open paren close paren open paren close paren", backwards it is "close paren open paren close paren open paren"
Yeah, you’re right. Writing it down character by character finally made it click for me 😅
Well, I definitely feel silly now.
Yes
I think it's often the other way around... senior devs (good ones anyway) tend to care more about overall correctness and clarity, where less experienced devs get fixated on minor nitpicks and subjective personal preferences.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.