Hacker News new | past | comments | ask | show | jobs | submit | spacekitcat's comments login

That feels like a bold and possibly dangerous thing to say without evidence.


The former Reddit employee in question accused the Green Party in the UK of transphobia, after they discovered she hired her own father as an election consultant, under an alias. At the time, he had been charged with rape and child abuse, and has since been convicted.

This is all public information.


Doesn't seem like the accusation stuck. And it would be very easy to point out she did it before.


  Doesn't seem like the accusation stuck.
Are you unclear on the definition of "convicted"?


Read their first sentence again.


How is it bold and dangerous? A decent chunk of people accused any person who criticized this person as transphobic. This has happened with other LGBT people so there is a history of this happening in the past.


I think an important factor is how fast the team need you to hit the ground running.

Where there’s time for new developers to get up to speed with a new tech stack, I completely agree with you.


I think the biggest hurdle going from Java to C# is how you think about asynchronous code, more so for desktop software. My last role was C# with me coming from Java and I got a few rude awakenings.


Eh, you don't get to control the language of others. If someone wants to say PitM, that's their business.


You can also call it SITC (someone in the centre) attack if you will, but the point still stands - it impedes communication.


So long as you expand the acronym in the first use, no one reasonable cares.


The same reasoning applies to "single letter variable names are fine".

Humans aren't computers. They have a finite number of concepts they can keep in their head. Using existing conventions leads to better understanding as it allow folks to get through a discussion without having to backtrack as often.


I care. Always preferred well established acronyms that everyone is familiar with.


From this day forward, I will refer to this sort of attack as a PiTM attack. Not much you can do to stop me I'm afraid.


> no one reasonable cares

I care. There's no need to make challenging technical texts more obtuse to read by reinventing all the terms.


I’m jealous that older generations get to say they wrote their first program on iconic hardware. Computers of my time were much faster, but they were very generic.


I started programming in the early 80s, and started programming professionally in 1987. The biggest difference between early micros and PCs was that most early micros had better documentation in the box than the PCs did. For example, a C64 or a TI 99/4a had documentation that would take you from beginner to being able to access hardware features. The PC, on the other hand, you had to buy books from third parties to get that level of documentation. To be fair, the PC had a lot more going to document.


This resonates with me. My first computer was an Acorn Electron. IIRC the user guide included things about IRQs, 6502 assembly language, and even details like using 'two pass assembly' to assemble a program which referred to a something before that thing had been defined.

My first PC came with instructions on how to connect the keyboard, mouse and monitor. I recall thinking it was really strange that something could be sold without instructions on all its functions. Until then every electronic device I'd bought came with instructions that were 'complete' in the sense that everything you could do in normal use was documented.


I started in 84 on a PCjr. Had the PCjr Technical Reference manual, which was amazing. It even had the BIOS assembly source in the back of it.


IBM did a great job with their product. The clones on the other hand... well, sometimes you were lucky to get a ziploc bag with 20 page warranty and how to install documentation from each of the parts.


Yes, I feel a bit robbed by 90s computers when I pick up old manuals or cheap programming books for things like the BBC Micro.


A lot of the newer Apple products are fairly iconic as well: iPhones, iPads, MacBook Pros, and a lot of people consider some of the iMacs such as G3 or G4 to be iconic as well. So there's still contemporary iconic hardware for someone to write their first program on :)


I mean, I'm 32 and I programmed on one of those as a teenager. If you do the math, yes it was 20 years old at the time, but I had a blast anyway.


We do RFCs, I dislike the concept. It feels like an extension of this troubling trend of taking away autonomy from engineers.


As a woman in tech, I feel that it isn't actually a meritocracy.

I think people have a habit of assuming men did the real work in a project, so they get a disproportionate share of the credit. People also have a habit of pushing women towards front end work, making the assumption that men are more 'technical' than women. It can be difficult to watch men get all of the credit for your blood, sweat and tears. It's especially bitter when they then say it's a meritocracy and you feel like saying 'what exactly did you contribute to this?'.

The concept of a meritocracy sounds nice on paper, but I think it ignores how humans work. The first issue is that I don't think we are especially good at identifying the best unless it's very easy to measure (sport for example). The second point is that it takes work to overcome your own biases and I think this feeds into how we evaluate 'the best' more than we like to admit.


Meritocracy is a good thing and we should never stop striving for it. The problem isn't that some strive for meritocracy, the problem is when people argue that they are meritocratic when they aren't. It is pretty easy to argue that there is plenty of merit in hiring women, like adding diversity to teams has benefits and so on, I don't see why you need to argue against the concept itself.

> The concept of a meritocracy sounds nice on paper, but I think it ignores how humans work.

Not really, the concept is nice both on paper and in reality. The most successful companies in the world today are much more meritocratic than most organizations that preceded them, they produce great results using it, the concept works great. And I don't see why you think it wouldn't, we humans have two signals, merit and bias. Without merit we just go by our biases. The problems you describe doesn't come from focusing too much on merit but too little on it.


I think proponents of meritocracy are naive.


People who think that white men will hire more minorities and women if they focused less on merit are naive.


Striving to build an environment where effort is made to attribute credit where it's due and to strive for equality of outcome for all is what we need to do. You're still picking the 'best person for the job' according to your own biases for what constitutes the 'best' (because how else could it work?), but you're also making an effort to ensure that your team/department/company isn't just all white (straight etc) men.


> Striving to build an environment where effort is made to attribute credit where it's due

That is what meritocracy is all about though.

> strive for equality of outcome for all is what we need to do

This is your bias speaking.

I got my job at Google by doing well on online coding competitions. I didn't do it with anyone else, I just sat at home and practiced on my own. Anyone could have done that. Show me a single woman who did well enough to get a t-shirt from the main google code jam competition but failed to get a good tech job and I could see your point, but I don't think there are any.

More importantly you'd expect that women would flock to those more objective ways to get into the industry, however it is the other way around, competitive programming is almost only asian and white men. Asians love it since it is a way for them to circumvent the bias against them and get jobs at Google or equivalent, why can't women do the same? And if women refuse to do the same work I and many of my peers did to get in yet still say I got in via privilege why should I take them seriously instead of just assuming they are biased against me? It isn't like women have less time as students than men have, they just choose to spend it differently.


Listen, I know what I’ve experienced.

Edit: No actually, I can't understand what this is? You are trying to convince me my experiences are wrong. You don't seem to actually want to understand my point of view, so what is this? Why are you wasting both of our time like this?


> You are trying to convince me my experiences are wrong.

No, I am not, I agree that there are many situations where women are not taken seriously due to their gender and assigning project credit is one of them. I 100% believe that has happened to you, that is wrong and we should try to do something about it. If you want that then you support meritocracy instead of biasocracy. However I'm trying to convince you that this statement is wrong:

> strive for equality of outcome for all is what we need to do

Men and women are different on average, maybe because of socialization etc but fact is that today they are different. My path relied on anonymous interactions online, so is by far the most friendly for marginalized groups. However marginalized groups like women are basically non existent on that path. That proves to me there are more differences than just discrimination. If you want to hire someone like me you wont find a woman, as there are hundreds of men for every woman with that background. Now you might not want to hire a person with those skills, but those who do will not find women to hire. And not because of discrimination, they don't even try to work for it in the first place.


This is why you've been pushed towards front end work and denied the credit for tasks that might put you on a path to power. Those above you can sense what you'd do with it. You'd say: "My experience has been this, and none of you can argue with that, so here is what we're going to do to make up for the injustices I experienced. Deal with it". The equality of outcome you so desire would be you and everyone underneath you unemployed, whole organizations gone bankrupt, and entire countries: a gulag.


Big brain comment here.


So you are basically describing a malfunctioning meritocracy, where the function that determines merit is corrupted by biases. Seems like the solution would be to remove biases (e.g. in case of coding interviews, do blind interviews instead of/in addition to in-person ones).

As a side note, my experience in all the teams I worked at (tech in SFBA and Seattle) is that white men are a small minority, and if you exclude Eastern Europeans barely exist at all. Even if you exclude the usual suspects, I'm pretty sure I've had more coworkers originally from North Africa than originally from North America :)


What is the problem with hiring a white person vs a blue person if the white one is better? And vice-versa, hiring the blue one if he is better?

If you want to hire white workers regardless of their competence, then you should start a company.

"Better" means that they have a high probability of doing the job as the employers sees fit. Don't go nitpicking on defining 'better'. If you do, you're not suited for the job of deciding who to hire.

And if you are suggesting that hiring process is biased then you are right - people are not robots.


The person you’re replying to didn’t say the article was wrong or try to discredit with an ad hominem attack, I interpreted as questioning if we really want to hear the opinions of someone so unsavoury and untrustworthy. It’s not to say his character invalidates his past research.


IMHO it is an ad hominem attack. Assuming we want to hear correct arguments, "We won't listen because you're icky" is ad hominem.


While we're playing this silly, overly reductive logical fallacy bingo game, IMHO, your reply is a straw man.


Could you help me steel-man it then? What do you think is the better version?


How do you establish that a binary is trustworthy?

I know what I do, I generally try to find user reviews, but someone had to install it first.


You can upload the binary to virustotal and see if it got flagged.


Oh, that’s an interesting tool. Thanks.


I found myself without a job a few years ago and I really needed a lifeboat. A job just sort of came to me on Linkedin with very little effort and while it wasn't the best, it was what I needed at the time.

It's worth having a Linkedin profile, but it's car crash of a social network.


This sums it up for me as well. The website itself is garbage, but I keep a profile on it just in case I need it down the road.


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: