2,193 karma · joined July 1, 2010
I didn't think that way until very recently, and then something occured to me: limiting things to 80 characters means you can fit more vertical strips of code on your screen without line breaks. On a 1920x1080 screen with a 6x13 font[1], I can split vim into 4 vertical strips each of which are 79 characters wide. It's not perfect, but it means that my screen is filled with code instead of whitespace. Keeping code width low is like dyanmic-range compression[2] for code.
[1] -Misc-Fixed-Medium-R-SemiCondensed--13-120-75-75-C-60-ISO10646-1 (I have yet to find a more readable font with those metrics, and I've looked hard) [2] http://en.wikipedia.org/wiki/Dynamic_range_compression
Related: https://www.google.com/search?hl=en&q=is+this+the+iphone...
Probably going to get downvoted, but http://www.reactiongifs.com/wp-content/gallery/yes/shaq_YES....
I reserve the right to let people know who I am at any time and to deliver it how I please. I don't want anyone to tell me I should "let it emerge naturally." If I want to do that then sure, that's very tactful. But sometimes I don't.
The author has an obligation to do nothing. It is up to the audience to change their perceptions.
(for the sake of argument I'm going to assume you're male). Imagine you moved to a country with a different language, and your given name sounded feminine in that language. Every time someone met you in person they would look at you strange and go "oh, I'm sorry! I thought you were a woman!" Perhaps you would be assigned to the female dormitory if you studied abroad there, and embarrassingly had to file paperwork to change that.
Would you want to make a small note on your email signature saying "I'm a man!"? I know I would. This is something you would write about, because it kind of is an issue.
These are the kinds of things female developers have to deal with all the time: "wait, you're here for the conference? As a developer? I'm sorry, I didn't realize!" "Okay, but you're not like a developer developer, right?" This shouldn't be the case. The annoying thing is that if a woman writes a note saying "I'm a woman!," they get put in a different class of developer than if they left it off.
You're missing the point of the article. The point is that if she does 'highlight great articles from the women in tech,' then she would be labeled a "female developer" instead of just a "developer." If she doesn't do this, then she gets labeled a male developer. She would like to be labeled "developer," but the two options she can see lead to undesirable outcomes.
This has been said before, but the key thing to take away is the concept of "othering." The author would like to be seen as a developer, not a subcategory of a developer that is somehow different from the norm. Perhaps a better way to demonstrate is to take this to the extreme:
"Instead of highlighting great articles from brown-eyed people in tech, or linking to other brown-eyed people in the industry with well trafficked blogs and talking about their contributions, the author fell right into the category that perpetuates this problem."
Sounds pretty absurd right? Who cares what their eye color is. On the other hand, imagine if everyone got it wrong. Imagine if you had brown eyes but there was a 'default assumption' that everyone had blue eyes. You wouldn't want to make a fuss every time people got it wrong, for fear of being "that person" who is annoying and pedantic, and "hey, it shouldn't matter! Technology is eye-color blind!" But if you don't do it, it gets a little grating when EVERYONE assumes you are something that you're not. It's a catch-22.
The solution is to remove the default assumption that developers are male. That is something that you, not the author, have to do.
Before this, you could only hook in an AT&T phone into the jack, and you had to rent that from AT&T.
[1] https://play.google.com/store/apps/details?id=net.cachapa.li...
Here is a fun word: 'microclimate.'
"Due to [SF]'s varied topography and influence from the prevailing summer marine layer, weather conditions can vary by as much as 9°F (5°C) from block to block." http://en.wikipedia.org/wiki/Microclimate
I'm a little spoiled having lived in NYC directly across the street from a 24/7 Dunkin' Donuts.
Still no late-night coffee (with wifi!) but that has a higher chance of springing up in the city than in Santa Clara.
So this is a really hard idea to get out to someone, and is the core of a lot of the issues here: a lot of issues women face in technology are issues that men have never experienced. They usually aren't aware that these issues even exist, and probably couldn't brainstorm them if prodded.
Here is a thought experiment. You're writing a unit test framework, and the output of your test is like so: http://i.imgur.com/jIsR8.png (sorry for the non-terminalness)
You pass this off to your friend to see what he thinks. "How do you tell if the test passed?" he asks. "What do you mean?" "I can't see if a test passed or failed. I don't get it." "What? All the information you need is right there!"
Turns out your friend is colorblind. Chances are, you didn't intentionally make this hard for colorblind people. It simply wasn't on your radar. Assuming you aren't colorblind, you go through your whole life discerning the difference between green and red and simply assume everyone else does too! The difference is that when someone brings this up, you don't go "nuh uh! We all see exactly the same way! I don't see what barriers there are for anyone to tell the difference between red and green." Yet this is exactly the response you gave above. (Don't worry, we all do this to a degree).
The point is, there are lots of subtle differences that people with different backgrounds view the world through. It's unrealistic to accommodate all of them, but in order to be a better human being you have to stop and listen when someone tells you something that is outside of your experience. So when you say you're 'not really sure what barriers there are for anyone,' well, there are a lot. Especially for women. That's why we need sites like this.
If you're interested in a long but very well written piece, I highly recommend Ellen Spertus' MIT AI Technical Report on this subject: http://people.mills.edu/spertus/Gender/pap/pap.html
How could you read comments on HN, reddit and youtube and not be depressed?
Ken Thompson won a Turing award, dude.
Yes, which is awesome.
> If you think about how return values work in C you'll note that it's usually some subset of the range which is defined for an actual value and some subset defined for an error condition.
This would be an 'in-band' error, as opposed to 'out-of-band.' It's terminology borrowed from communications theory. You also see it used to describe an 'out-of-band' console that is a secondary way to SSH into your machine if your network is hosed.
> Also, I didn't mean that Go should have innovated in PLT, only took advantage of innovations already established.
I think the point is that this is intentional. I love super high-level languages, but they're experimental for a reason -- things haven't 'settled down yet' and until they do, it will be difficult for the average person to reason about what is going on. Take garbage collection: this was technology that had been around for decades, but computers and garbage collection algorithms had to be sped up and tuned before general adoption. Large systems demand predictability and integrity on nearly every dimension. Luckily as time goes on, the experimental stuff becomes the expected; advanced programming language theory gets built into larger systems and we all benefit. Go is part of that evolution.
"Go is not meant to innovate programming theory. It's meant to innovate programming practice." I really like the out-of-band errors since they make control flow very explicit. With languages that rely on exceptions a lot (python, for example) I feel less in control of my program since 'anything can happen' remotely from my code.
Chrome's shortcut for 'reopen recently closed tab' is ctrl-shift-t. If you open a fresh browser window and do that, you get your tabs from the last session.
real talk: have you ever worked on an 'embrace, extend, extinguish'[1] feature or are rank-and-file engineers shielded from that? the only microsofties I know worked at MSR and from what I understand that is a much different environment than actual microsoft. kind of curious what it's actually like in there[2].
[1] http://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish
[2] I tend toward the side of linux zealot so I'm trying to soften my tone here
yeah, tupac is rolling in money right now
That image told me that real people were behind the site, and strangely won my loyalty in a sea of identical clones. The new site removes that and feels pretty but boring and forgettable. Even their twitter icon gives me the "generic social media company feel": https://twimg0-a.akamaihd.net/profile_images/2260560652/twit....
This is a phenomenon I've seen with a lot of sites as they get big and overhaul their site with a "real" designer who wants things "to be cleaner". Things usually come out more bland...