Ah yes. Life before Agile was wonderful.

^ yes, this exactly. It was the equivalent of living on the dark net in the eves. Total Wild West.

Not all > 45 tho. I’d say 40-55 or so who were also “nerds” or “geeks” as kids.

Care to elaborate?

I have a girls name and my last name is a very popular Asian female name too.

My entire life I get misgendered on phone, email, chat. It’s not a big deal. Hell, it can be an advantage - I’ve gotten more than one job interview because they expect a woman.

No damage on friendly fire

*brake

Closed as a duplicate

Yeah and it won’t tell you that it hasn’t seen this pattern before. It will just make things up out of the blue which seem like they might be correct.

Stay away from ChatGPT for bleeding edge things.

Be careful with this dangerous logic. You’ll get pitchforked.

All this sensitivity being mainstream is new to me. It came from all angles in all aspects of life very suddenly.

Yes you can find some things happening in the past, but sweeping changes were made in the 2020-2022 timeframe.

That fact doesn’t minimize anyone’s prior efforts, thoughts, feelings, actions, movements, or otherwise. The attempts to fix the English collective masculine date back to 1795.

As early as 1795, dissatisfaction with the convention of the collective masculine led to calls for gender-neutral pronouns, and attempts to invent pronouns for this purpose date back to at least 1850, although the use of singular they as a natural gender-neutral pronoun in English has persisted since the 14th century.

Yeah, 2020 is the time period I’m referring to. I had never heard of it being a thing until George Floyd and BLM movement in 2020, then GitHub changed in response to that.

I’ve been in IT for 35 years. And I never heard a single negative thing about branch names and master/slave terminology until 2020.

Perhaps you think that was set aside because IDE hard drives are dead.

Sensitivities during Covid ran high. A lot of things changed then. For instance in the software world removing the name “master” from git usage, and on the TV Show Survivor, the host not saying his famous line “come on in guys”. At the same time pronouns became a huge thing, and these seemingly gender specific or sensitive word terms were targeted.

You are correct, there was a round of this in the 90s or so, where job titles like “waitress”, “stewardess”, “policeman” were all adjusted. I see that as a very different round of language change.

3 years ago, “man” in that context was considered gender neutral. More recently tho a lot of stink is being made about little language things like this. Theres no replacement word to use.

Me too. But due to the non linear storyline I typically jump around a lot

What OS do you run? Are you planning on sharing this app with others? Should it be a web app?

Happy to help!

In my 30 years of experience, it is usually the devs.

Yeah then you’ve got security problems. If a maintainer pulls a package, you wouldn’t want some rando able to push a new one in its place.

I’m well aware how async works in the single threaded js environment. All code blocks the main thread! Calling await on an async operation yields back.

You’re right, async is commonly mixed up with multi-threaded. And in fact in many languages the two things work hand in hand. I’m very aware of how it works in JavaScript.

We are agreeing. Don’t need more info.

Tell you what, though-- feel free to have the last reply.

😒

Yes I’m simplifying a LOT, but in the context of background web calls, that was what callbacks became so important for. XMLHttpRequest in IE 5 sparked the Ajax movement and adventures in nested callbacks.

Prior to that, the browser had window.setTimeout and its callback for delays and animation and such - but that’s it.

The main purpose of all this async callback stuff was originally, and arguably still is (in the browser), for allowing the ui event loop to run while network requests are made.

NodeJS didn’t come into the picture for almost 10 years or so.