That’s something to work on. You’re not immutable.

If you accept rejection with dignity, it’s not that big a deal. Don’t be a creeper. It’s not that embarrassing. And if your friend group is cruel about it, that’s good to know. They’d be assholes in that case, and you probably want to find out they’re assholes in a low stakes situation.

She could ask you out. But if you just wait you’re giving up your initiative. Use your agency.

…yes? That’s what you have to do. Maybe she says no. Maybe she says yes. Doing nothing definitely won’t get you anywhere.

You know how scam emails intentionally include mistakes because they want to filter out smart people? Same idea.

Reasonably smart people will see this and go “this is garbage”. The idiots will go deeper, and become loyal gop voters.

I don’t think “every single problem … must be reduced down to an individual failing” is super common, but sure, some people refuse to recognize systemic problems. There are loads of people who say racism isn’t a problem, for example, and that’s bad. Kind of off topic from childhood development and people who refuse to admit fault when it is plausibly their fault. (And saying you’re late because there was traffic because the city refuses to build effective mass transit may be technically true in a sense, but it’s also kind of useless, maybe even counter productive, in the moment where everyone else is waiting for you. Leave earlier. Use the agency you have.)

A lot of people here seem stuck on the details of the metaphor instead of focusing on how some adults refuse to ever consider they are wrong or at fault, and that’s a real problem in the world. You probably know someone who never admits fault for anything. If they’re late, it’s because of traffic. If they lose in mario kart, it’s because the controller is bad. If they get lost, it’s because the GPS is hard to understand. Never their fault.

“Use a different language” is a common defense of javascript, but kind of a weird one.

Yeah. My last job, a PR with commented out code typically wouldn’t get approved. Either leave it in version history, or stick it on a branch

Call the function from the if block.

Now your tests can more easily call it.

I think at my last job we did argument parsing in the if block, and passed stuff into the main function.

Anyone entering through web development. If you’re self taught or did a “coding boot camp”, it might be the only language you’ve used. A lot of places use it for backend stuff now, too

I don’t know about “fine”. It has a lot of weird stuff baked in. Hoisting. Unexpected type coercion. Too many ways to loop over something and I always forget which one is which. “There’s more than one way to do it” is kind of a recurring problem, come to think of it. Several function declaration syntaxes. Dot notation AND bracket notation for objects.

Also it will forever bother me that object keys aren’t quoted.

const foo = "hello"; const bar = { foo: "world" }

That should be, in my mind, { "hello": "world" } . It’s not. It’s { "foo": "world" }

But if you want to do that, you need to do const bar = { [foo]: world }. Which looks like your key is an array with one entry, a string with a value of “foo”

You also end up learning a whole framework, with its syntax and idioms, every couple years. Angular. React. Redux. Whatever.

There’s also a lot of people who have never used anything else, and want to use javascript for everything.

Javascript is basically D&D. Wildly popular. Full of legacy jank. People try to use it for anything even though there are better or more specialized tools.

This is an ancient joke but they replaced the original pigeon with a blue thing instead. :confused:

At one of my old jobs, we had a suite of browser tests that would run on PR. It’d stand up the application, open headless chrome, and click through stuff. This was the final end-to-end test suite to make sure that yes, you can still log in and everything plays nicely together.

Developers were constantly pinging slack about “why is this test broken??”. Most of the time, the error message would be like “Never found an element matching css selector #whatever” or “Element with css selector #loading-spinner never went away”. There’d be screenshots and logs, and usually when you’d look you’d see like the loading spinner was stuck, and the client had gotten a 400 back from the server because someone broke something.

We put a giant red box on the CI/CD page explaining what to do. Where to read the traces, reminding them there’s a screenshot, etc. Still got questions.

I put a giant ascii cat in the test output, right before the error trace, with instructions in a word bubble. People would ping me, “why is this test broken?”. I’d say “What did the cat say?” They’d say “What cat?” And I’d know they hadn’t even looked at the error message.

There’s a kind of learned helplessness with some developers and tests. It’s weird.

Is the backend Python and the frontend JavaScript? Because then that would happen and just be normal, because Boolean true is True in python.