Shit's wild. The IT guy and I loved reading pajeet programmer resumes.
To be clear, this isn't an Xenforo bug. Quoting long posts used to work just fine; Null specifically broke it because he was getting angry that people were quoting entire long posts just to add a sentence or two at the bottom. The cure is worse than the symptom, though.
Pajeet problem is mainly cultural. They are mentally incapable of admitting to not know what you mean and would rather waste your and the company's time doing their best interpretation of what you said.
I encourage people to not use phrases like, "do you understand?" after explaining something, and instead something like, "Now that I've shown you X, you go ahead and try", at which point they get to do the demonstration. That way it's immediately apparent where the explanation and/or knowledge gaps are. It is a very painful process for both parties at first, but once you get used to passing knowledge this way, it helps everyone out. As a bonus, the people who can't/won't learn will eventually stop coming to you for help unless there's absolutely no other recourse for them. This, and requiring any inquiries to be through e-mail or meetings scheduled on calendars (instead of bullshit IMs and impromptu phone calls), has reduced my interaction with pajeets to almost nothing, despite them being roughly 2/3rds of the programming team.
There is also the "can you repeat it" for verbal talk but yeah. In the end you are just micromanaging something only slightly more complex than a general compiler.
Lol awesome. And it's the proper temple menorah too.
The hidden secret of Hanukkah is that the only had enough lamp oil for one day, but they had enough parentheses to last for like five fucking decades.
What industry? I don't think you have to worry about the troon thing so much unless you're going to work at Big Tech/FAGMAN.
The interview process goes two ways. They meet the candidate and assess his or her skills, and the candidate meets the people he or she will be working with. If you get the feeling that you don't want to work there, it's just as much your right to decline as it is their right to opt not to offer.
I think php is the one that attends the synagogue more often.
I can think of a tip for you, and for gals and pals in a similar situation too. When you're investigating any place, check their people and work culture, with this you can spot red flags way ahead. For example if they've hired crazies, they have adopted a ridiculous CoC or their socials are pozzed then you should just ignore the place. I got a handful of horror stories from friends and acquaintances about how agonizing is to work with these foul people, specially troons.
You will get hired based off diversity, full stop. There is no company hiring software developers who will not take one look at your resume and, assuming you appear halfway competent, hire you because you're a woman. What you can do is, once you are hired, not be a massive piece of dead weight that makes it obvious to everyone you work with that you can't hang.
Honey, as others said it really doesn't matter why they hire you. If you don't want to be a diversity hire, just hone your skills, deliver quality code, and be the best you can be overall. That's all.
Another trick is that at a smaller company, you'll probably be hired by a non-tech-savvy manager who will have no way of judging whether you're a "good" coder or not so long as the deliverables get done on time, so for women (or men) just starting out who are worried about others judging their work harshly because they're new to the industry, getting a couple years clocked on the resume with a small company might be the way to go.
People will be suspicious at first that you're a diversity hire, but they'll be relieved once they realize you're a valuable member of the team.
