102 karma · joined September 9, 2018
If it's okay to ask: has anti-white racism been a significant problem for you in your life? For example, are you a white person who experiences anti-white bias from people you interact with?
Say I was organising a poetry meetup. There are many aspects to making its attendees enjoy themselves, but evenly distributing my effort would not create the most equitable event. If I want the event to go well, most of my effort should probably go to people for whom the barriers are biggest. This could involve making sure the venue is accessible to wheelchair users, extra encouragement for the person who seems to never have heard that their poems can be worth something, or creating a speaking convention that benefits everyone equally, but puts the most burden on those who are bravest and loudest.
> Your remedy requires institutionalizing the sorting of individuals into groups.
> It will be very hard to get out of that situation.
Interestingly, not in the case of what the posted article is about! Facebook can decide on its own to give extra priority to checking comments for (what its moderators consider) anti-black racism, and it's also the kind of thing that will eventually make itself unnecessary.
It's not enough to say, okay, let's all be fair from now on. I think this misses the acknowledgement of all the past violations of this principle, and any attempts to make this right.
I'm all for opening or abolishing borders (and keep recommending No Wall They Can Build (2016), free as a pdf to people), but I'm not sure if this is simple or that thing you said.
Even though there's frequently value in adding whitespace to programs, many of them are just fine as one liners :)
e.g. this gets the title of a webpage for you: ``` $ perl -Mojo -E 'say g("mojolicious.org")->dom->at("title")->text' ```
You could also become really, really good at using a text editor, it becomes a bit of a game and it's going to be useful for as long as you are planning to type.
Hello! Do you know UNIX and how to responsibly manage compute, and want to work in an academic environment?
You could move to Cambridge and replace me:
https://jobs.sanger.ac.uk/vacancy/senior-bioinformatician-wo...
In fact you should do better than me, because it now says senior and I wasn't a senior. I have really enjoyed working at this job, and I'm leaving it after a year and a half because I'm moving to the United States.
It's for a resource with genomes of parasitic worms. You'll support a small community of researchers that study host-parasite interactions, search for candidate new drugs, and in general are worth supporting.
The bread and butter of the job is writing and running code that moves data around and runs heavy computations on it, resulting in a new data release every few months. You'll help researchers at Sanger with their use of the resource, reply to helpdesk tickets, write to ask people for data, and go to conferences once or twice a year.
You'll be a Bioinformatician, not a Developer, which means your code can be as good as you want it to be, but there are no brownie points for it. There is opportunity to develop more stuff - I've had a half a year long greenfield project - but it's more important that releases happen, and that the data is correct.
The team is tiny, and the amount of good stuff you do will be limited by how much time you have, so this really suits someone who can handle responsibility well. It helps to know Perl and have bioinformatics experience but you can learn both on the job if you meet other prerequisites.
So, using text files for storage could be really good, if possible. A desktop application could be written as a single process binding to a port and displaying a HTML-based GUI could work as a console, probably in all kinds of unforeseen ways.
As for the language, I would write it in Perl. There's gonna be an interpreter in an every UNIX based box for many years to come, and the community thinks backwards compatibility is a feature. I don't know if they'll keep it going for a hundred years, but we might also have bigger problems than keeping applications going.
I'd say do whatever you do already with some extra curiosity and long-term view thrown in. You're probably using a text editor in your current job. Why not take time to learn some shortcuts in it during the next couple of tasks (and do them slower).
You're probably also using Unix. You could learn what actually happens when you do, say, `ls`, if you don't know yet.
Reflect on what you're doing and what you just did, what was inefficient or bad, and whether you could have done it better - that's always good for learning stuff.