> Uncaught TypeError: Cannot read property 'childNodes' of undefined
at _VirtualDom_addDomNodesHelp (app.js:3616)
at _VirtualDom_addDomNodesHelp (app.js:3624)
at _VirtualDom_addDomNodesHelp (app.js:3624)
at _VirtualDom_addDomNodes (app.js:3540)
at _VirtualDom_applyPatches (app.js:3647)
at app.js:3937
at updateIfNeeded (app.js:3972)
I wonder what kind of backlash would be faced had the Nintendo product not existed and a console manufacturer proposed, in 2020, to name their handheld the "Game Boy".
Don't be so sure. A name like Game Boy could be seen as assuming the gender of the gaming audience, and alienating females from playing games. It's stupid, I know, but that's current-year thinking for you.
The two genders people backlashed against the unlimited genders and there was then a war between them - the unlimited genders want references to the two genders to be removed as they seem to promote the viewpoint that two genders exist and not unlimited.
Companies and powerful organizations are wary of the unlimited genders people as there is a worry that they may control enough economic power to make things unpleasant, therefore any organization that is not strongly on the two genders team chooses no genders as the compromise in the war.
If somebody wants to be a girl or a boy, or some creator wants to call their creation a boy or a girl - what's wrong with either? Again, we're spending a tremendous amount of energy and attention on things that future generations will laugh at. This is no similar than the billions of people who can't learn to wear a face mask properly. We're the laughing stock of the future. Should I refer to my boy or girl to they to be PC-compliant, too? How shameful is to associate your children with specific genders, right? As typical flawed humans, we're blowing everything out of proportion, we keep pressing and pressing, until matters burst into uncontrollable chaos!
The solution is to not comment on such issues and downvote and potentially flag (when appropriate) people that spend all their time writing about that instead of things that actually matter.
Since genders are classifications if everyone has a different gender it isn't a useful classification. So "too restrictive" -> "not very useful" -> "stop using"
PatchGirl felt kind of neat to me!
Back then, I pictured a young rebel pirate girl on a boat filled with adults (postman, pow, insomnia, ...) and she just looked cool in my head :-P
Sounds like a great way to integrate a strong female character into your product somehow! Why not use your idea as the logo?? The name is gendered, but the logo is very bland and ungendered. Seems inconsistent.
I see your vision now, and I get everyone's "this is PC nitpicking gone mad!" reactions - but I think it's more subtle (of course it's totally up to you). "Girl" works great as a superhero name, but for tool for doing serious software development it feels a bit dated.
"Girl" has a lot of historical connotations when applied to real actual work. It was a way to belittle the importance of people's skills and organizational value. When I first read "PatchGirl" I saw switch-board operators, not superheros - because it sounds exactly like a name that would get applied to women's work in the 1950s.
The same is true for "boy": if you want to imply someone's not a man, you call them "boy"... but no one after the 1950s would do this in an office setting unless they were being antagonistic. Again, it's fine for a superhero!
I think that's why some people will be against the name. Words are powerful, and have been used powerfully in the past. If you're not aware of the past (or not adversely affected by it) then it seems like a stupid nitpick - but to some there's a negative reaction to seeing history repeating.
I worked at a salmon cannery in Alaska for a summer. On the canning line there was the patch station, staffed by “patch girls.” Open cans, freshly filled with fish, would come down the line to each station at about 70 per minute. They were automatically weighed. If they were too heavy or too light you’d “patch” them with extra fish to bring them on par.
This station was very fast paced, precise, and very stressful. And had a small pay increase to account for what a demanding position it was.
The role was open to anyone but when I was there it was all women (and usually was). I was told it was because they most often had the ability to stay calm in the never ending onslaught of cans and still do precise work for hours on end.
I (as a man) worked on at this station for a few days, but couldn’t handle it. It was bonkers hard and those women were beyond impressive.
I've never seen any other business advice, backed by evidence, downvoted and kill on this community for literally any other subject. It really says a lot.
People would rather bury the idea that this industry is male dominated then make sound business decisions.
- and it is not backed by evidence that this is even a problem
- or that the "solution" will solve anything,
- it is backed by anecdotal evidence of a thing many of us dislike intensely: namely innocent organizations and individuals being hounded into crazy things because someone thinks someone else might get offended.
I say as Rowan Atkinson: feel free to insult me!
When I was young and vulnerable people did that to some small degree anyways and now I am old enough to don't care and/or get back at them, and meanwhile it has been an invaluable lesson.
In my case: Just stick to the facts, and don't accuse me of things that aren't true.
Or: in other words, if someone suggested your codebase should have comments in Russian because "think of the Russian children" it would be downvoted to.
What are your credentials? specifically related to the fact that github is moving away from master/slave terminology. Do you feel like their executive team is acting on unsound business ideology?
This seems to be a tool to allow me to semi-automate repetitive tasks that access a REST API; is that correct? Can I download it and fill it in with my own endpoints, etc?
Kind of :-)
The idea behind PatchGirl is to allow developers to combine REST and SQL requests to populate your database to a desired state.
The goal is to make "database seeding" and "API testing" reproducible and ease manual testing :-)
One comment based on a discussion I was having yesterday on this subject, I’d be careful of the term seeding. I think of seed data as data required for the app to function properly. For example, I seed my application database with a system user account or other system specific data.
I’d contrast this with test data which is used to provide a consistent data set for reproducible actions (usually unit or integration tests).
I'd say the definition is whatever definition the team you work in uses. For example for me at work, seeding = automatic database setup for a test system with example data
> I'd say the definition is whatever definition
> the team you work in uses.
No, the definition of industry terms is the way they would be understood by other people in the industry. Seeding is understood to be critical data such as area code lists and timezone information.
> For example for me at work, seeding = automatic
> database setup for a test system with example data
You're not wrong. Seeding _is_ automatic database setup, just not only for test systems.
>No, the definition of industry terms is the way they would be understood by other people in the industry. Seeding is understood to be critical data such as area code lists and timezone information.
That's kind of the point. Ask three different people in the industry, get three slightly different definitions, unless they work in the same team.
I don't get the gender backlash here, personification has been a thing for a long time and there doesn't seem to be any malfeasance (intended or otherwise) here. It's not lewd, doesn't play to stereotypes, etc.
To me, a basic litmus test is whether you could easily swap the gender without reworking anything. If you can't, it's probably offensive, if you can it's practically gender neutral (naming aside). It's not a catch all, obviously, as it's no replacement for awareness of history, culture, stereotypes etc.
It's easy enough to maintain a rebranded mirror synced to upstream. Instead people seem to want to take offense just for the sake of virtue signaling.
Can you point me to any examples of that stereotype? Historical employment figures, long form discussions, etc? I've genuinely never heard of that one, and considering the dominant solution in this space is Postman an alternative, female gendered solution could be argued as inclusive.
I've been in web development for over a decade and have never heard of this. All of the QA teams that I've worked with in the past have never showed any preference for one gender over the other.
Scenarii is very pretentious. I know you are going with the Italian plural, but it's not an English word. It's really out of place on the landing page.
48 comments
[ 3.6 ms ] story [ 98.6 ms ] threadexamples: factory girl was renamed to "factory bot". https://github.com/thoughtbot/factory_bot/issues/921
github is renaming `master` git branches to `main` https://www.zdnet.com/article/github-to-replace-master-with-...
Companies and powerful organizations are wary of the unlimited genders people as there is a worry that they may control enough economic power to make things unpleasant, therefore any organization that is not strongly on the two genders team chooses no genders as the compromise in the war.
Never realized that was why factory-girl changed its name... That's interesting thank you!
PatchGirl was initially only a rest client so it was just a stupid pun (because of postman). But it stick and now I like the name :-P
"Girl" has a lot of historical connotations when applied to real actual work. It was a way to belittle the importance of people's skills and organizational value. When I first read "PatchGirl" I saw switch-board operators, not superheros - because it sounds exactly like a name that would get applied to women's work in the 1950s.
The same is true for "boy": if you want to imply someone's not a man, you call them "boy"... but no one after the 1950s would do this in an office setting unless they were being antagonistic. Again, it's fine for a superhero!
I think that's why some people will be against the name. Words are powerful, and have been used powerfully in the past. If you're not aware of the past (or not adversely affected by it) then it seems like a stupid nitpick - but to some there's a negative reaction to seeing history repeating.
Girl just sounds better.
This station was very fast paced, precise, and very stressful. And had a small pay increase to account for what a demanding position it was.
The role was open to anyone but when I was there it was all women (and usually was). I was told it was because they most often had the ability to stay calm in the never ending onslaught of cans and still do precise work for hours on end.
I (as a man) worked on at this station for a few days, but couldn’t handle it. It was bonkers hard and those women were beyond impressive.
People would rather bury the idea that this industry is male dominated then make sound business decisions.
- hopefully IMO not sound business advice
- and it is not backed by evidence that this is even a problem
- or that the "solution" will solve anything,
- it is backed by anecdotal evidence of a thing many of us dislike intensely: namely innocent organizations and individuals being hounded into crazy things because someone thinks someone else might get offended.
I say as Rowan Atkinson: feel free to insult me!
When I was young and vulnerable people did that to some small degree anyways and now I am old enough to don't care and/or get back at them, and meanwhile it has been an invaluable lesson.
In my case: Just stick to the facts, and don't accuse me of things that aren't true.
Or: in other words, if someone suggested your codebase should have comments in Russian because "think of the Russian children" it would be downvoted to.
What are your credentials? specifically related to the fact that github is moving away from master/slave terminology. Do you feel like their executive team is acting on unsound business ideology?
This seems to be a tool to allow me to semi-automate repetitive tasks that access a REST API; is that correct? Can I download it and fill it in with my own endpoints, etc?
All PatchGirl's features are enabled by running a little proxy (called patchgirl-runner) on your computer which you can find here https://github.com/patchgirl/patchgirl/releases/tag/v3.0.0
Feedbacks are much appreciated!!
I’d contrast this with test data which is used to provide a consistent data set for reproducible actions (usually unit or integration tests).
Sorry if that’s a pedantic nuance
That's kind of the point. Ask three different people in the industry, get three slightly different definitions, unless they work in the same team.
To me, a basic litmus test is whether you could easily swap the gender without reworking anything. If you can't, it's probably offensive, if you can it's practically gender neutral (naming aside). It's not a catch all, obviously, as it's no replacement for awareness of history, culture, stereotypes etc.
It's easy enough to maintain a rebranded mirror synced to upstream. Instead people seem to want to take offense just for the sake of virtue signaling.
The stereotype that QA is 'women's work' is harming the industry.
Are you taking offense to people taking offense for the sake of virtue signaling?