Yes! Static and dynamic code analysis (for JVM a popular analysis tool is Findbugs, which is incidentally built into InrelliJ; another one that's okay that I've used before is Coverity Code Advisor) are what you're looking for I think, instead of API endpoint analysis, which is what fuzzing usually boils down to (e.g. What can I pass to this program to make it barf).
Interesting. We have done that for people of any gender in grad programs before when hiring for targeted roles suited for their specialty, but not to my knowledge for candidates by gender.
Yeah I'd rather have the teenager (or, actually, since it's been awhile since I saw a fast food clerk under the age of 40, the probable mom of several teenagers) for that reason.
Even though it may be more efficient for the customer to have the touch screen, I don't think service automation is so black and white.
As someone who has hired both males and females for junior and senior engineering positions at several companies, what you are saying is not the case.
The coding challenges and interviews are the same. The decisions of hiring committees I have been on have been actually in general weighted toward white men with experience more often than not, because many of the women I'm seeing are just out of school or with a little experience (which says good things about the future assuming they stick around).
However, I have seen race/gender used as the deciding factor between two candidates who are in all other ways equally excellent and suited for the role (that is, pick the candidate who is not a white male out of two whose skills and resumes and interview performance are equal).
Yeah after 1-2 presentations I built a template and just drop stuff into each slide I have defined. Then if I need more slides I copy the framework bit for a single slide. Super easy.
Wonderful, I had no idea what Noise was, or Signal for that matter, or NNCP despite reading the article. Thanks for the links! Guess I'll get back to my punch cards.
I've never done this with UUCP, but if you don't care about anonymity you could do two-way authenticated TLS (both client and server have and present certs).
Maybe you could do a ratcheting protocol like Signal does, instead, which might be better.
There's a couple ways to do this that might be sensible depending on whatever constraints there might be in a deployment.
This is a problem tech could solve. I don't see what stops us from monetizing saving the reefs via charging for eco-friendly tourism in pristine ocean.
I know what it means. If I'm paying for part of a house with a proper kitchen I will be cooking like a human at least two nights a week; no takeout and soylent here.
People can really easily abuse the Makefile ecosystem and write complicated, difficult to read, spaghetti builds. If something fails somewhere in the m4 macro forest while building on your specific machine, you're hosed for potentially hours or days while trying to figure it out so you can just build the damn project. The whole point of this kind of tooling should be to take some of the heavy lifting out of getting source code built, not add extra complexity to a project.
I've been working on and off with Make, C, autoconf, etc for ten years. Maybe if I were a full-time C or C++ person I'd have less trouble with this, but it seems rather excessive. The thing that most discourages me from contributing to certain open source projects is when I clone the repository and the build fails and I can't get the project to build in an hour or less of build-debugging time (and I'm not on a weird setup, I'm on a modern Lenovo with Debian).
> Breaking into tech companies is only about rehearsing Cracking the code interviews
Actually, all of the jobs I've had have cared very much about past experience and have asked about it in the interview. If I weren't actively contributing in certain open source projects, and hadn't worked with certain technologies, I wouldn't be where I am.
That's pretty polarizing. I think I said something to the effect of not developing the same, not "failing to develop any empathy at all". I and many of my friends have kids. They don't come into contact with each other more than occasionally, but the ones who are only children are much less willing to create something out of nothing and, say, play with the one toy that was available. Social situations, like having very close friends or cousins help, but something like preschool isn't 24/7. From observing the little guys, the ones who pitch screaming fits when their mum leaves them and I'm dropping off my kids are not the ones with siblings. And they're losing resources they haven't learned to share yet. I wouldn't say it's impossible for only children to learn empathy, just that it happens later, differently, and maybe doesn't achieve the same end goal of having a human being who's always had to share things 24/7.
Having more advantages is exactly the problem talking about. People, especially kids, need to scrabble a bit and fight for resources in order to learn how to treat the resources themselves and the other parties who might need them respectfully.
Oddly, I think outright banning fossil fuel refinement and usage would do more.
Being an only child seems to be a bit psychologically damaging. I could conjecture for pages here, but suffice it to say I believe one is better off having 2-3 children or none at all. Sure there can be situations like being raised closely with cousins or friends that are similarly beneficial, but kids absolutely must have close companions near their own age -- they don't seem to fully learn to be empathetic otherwise.
This is only the opinion of one person, take it however you wish.
I took a Lyft in Las Vegas where the driver was clearly mentally unstable (sounded and acted it), let us out at the wrong place in an unfamiliar neighborhood in a windstorm, and got out to piss in full view of both his headlights and the front of the wrong house. He then had to drive us to the right place grumbling the whole way. I've not ever had any ride/customer experience that even compares in confusion and intensity of uneasiness in an Uber, despite their shitty engineering work culture.
Being a hard worker is easier than being seven feet tall, though. I know it's disingenuous to say hard work will get you everywhere, but working your ass off and being confident about it will get you pretty far.
That's my plan actually. Once I have nothing to lose I'm going to tell the guy he's being an asshole to the women engineers and ask if he'd consider not doing that because it's a shitty way to treat anyone. Preferably with boss present.
The problem I'm having with it is he has to know this guy does this. It's not exactly subtle or I likely would not have noticed. He's been in the room before when it happened, and the two of them go out for drinks on Fridays and such all the time. I think it is not a problem for him or he would have pulled the guy aside and told him.
Trouble is, we are a fifteen person startup and my boss is a friend of that guy's from way back. I honestly would feel odd mentioning it. There's no way to couch it in "what if a hypothetical person..." because he's known this guy for longer than the company has existed.
One of my coworkers, when he thinks people aren't doing a good job, calls them ladies or girls. He also doesn't listen to the women on our team, insists on pair programming with them if he has shared assignments with them instead of splitting those assignments into subtasks like he does with the other guys, and is in general a nice dude to the other guys and treats the women like they're junior. If the rest of the men on the dev team behaverd like that, I honestly bet there would be no women on our team. I'm not sure how to approach him about it, but the women we work with don't seem to want to take assignments with him or interact with him, for fairly obvious reasons I guess.