Hover the top nav. Under "CI Runners" it's says:
macOS Runners Apple Silicon and Intel support
472 karma · joined September 3, 2008
macOS Runners Apple Silicon and Intel support
It even has audio clips of the two melodies.
http://www.wsjmediakit.com/files/uploads/201410/WSJ.com%20Au...
Also, this is the _actual_ audience not their _target_ audience.
"During the beta period you’ll only get an informational email. In the future, we will force exhausted apps to sleep until they have been idle for at least six hours of the past twenty-four hours." -https://devcenter.heroku.com/articles/dyno-types#dyno-sleepi...
Shouting fire in a crowded theater has been protected speech since 1969:
http://www.theatlantic.com/national/archive/2012/11/its-time....
> In 1969, the Supreme Court's decision in Brandenburg v. Ohio effectively overturned Schenck and any authority the case still carried. There, the Court held that inflammatory speech--and even speech advocating violence by members of the Ku Klux Klan--is protected under the First Amendment, unless the speech "is directed to inciting or producing imminent lawless action and is likely to incite or produce such action"
But what you describe does not sound like an honest or clear assessment of the world. It sounds more like depression. Which is real and serious and treatable.
The world is often tragic. It <em>is</em> wrong to live comfortably and be willfully ignorant to tragedy, but it is not wrong to take care of yourself and make yourself whole. So, yes, seek something meaningful to make the world better, and start by taking care of yourself.
http://www.theatlantic.com/national/archive/2012/11/its-time...
> In 1969, the Supreme Court's decision in Brandenburg v. Ohio effectively overturned Schenck and any authority the case still carried. There, the Court held that inflammatory speech--and even speech advocating violence by members of the Ku Klux Klan--is protected under the First Amendment, unless the speech "is directed to inciting or producing imminent lawless action and is likely to incite or produce such action" (emphasis mine).
As a disclaimer, I'm a programmer, and neither a feminist thinker nor a writer. I'm writing this as an ally. I also have quite a bit of privilege myself. So forgive me (and call me out) if don't make sense or sound ignorant or condescending.
I think you're saying that when someone says, "you have male-privilege," you hear "life must be easy for you." Privilege doesn't mean that you don't also suffer from other forms oppression or discrimination, and it definitely doesn't mean that you have it easy. You mention that you are discriminated against because you are "fat and ugly." It sounds like you've suffered from very real oppression -- every bit as legitimate as the OP's story.
I feel that part of the misunderstanding comes from the difference between the common and jargon meanings. In this context, "privilege" is a jargon word coming from feminist and social justice philosophy.
In common speech, if I say someone is privileged, the implication is that this person is well-off in some way. I imagine a person with money and political influence -- someone who has benefited wildly from their privilege. But in the jargon, it refers to "a set of opportunities, benefits and advantages that some people get and others don’t." (definition quoted from the blog post linked below) Someone recently told me the story of a black stock-trader who noticed he was being passed up for job promotions. When he investigated, he found that his white colleagues were playing golf together -- and becoming friends -- at an all-white country club. The bosses were not intentionally promoting white employees, but, because of the racist policies of an unrelated institution, the white traders got the privilege to build these friendships with their superiors.
I found this blog post really helpful. It gives a very non-judgemental and helpful introduction to privilege: https://sindeloke.wordpress.com/2010/01/13/37/
Here's an excerpt:
"Having privilege isn’t something you can usually change, but that’s okay, because it’s not something you should be ashamed of, or feel bad about. Being told you have privilege, or that you’re privileged, isn’t an insult. It’s a reminder! The key to privilege isn’t worrying about having it, or trying to deny it, or apologize for it, or get rid of it. It’s just paying attention to it, and knowing what it means for you and the people around you. Having privilege is like having big feet. No one hates you for having big feet! They just want you to remember to be careful where you walk."
I hope this helps.
Besides, he doesn't "fudge" V. He shows evidence: that violent crime decreased over the relevant period and argues that less violent crime implies lower average tendency to violence (V).
So I've identified a few ways I use my computer and I'm setting up a user account for each one:
* coding in Ruby
* coding in Java for work
* blogs and email (and hacker news)
* personal and household maintenance
If it goes well, I'll try to write it up in a blog post.
He begins by saying that 'interchangeable' is most important element to determining prior art: "more importantly, it had to be interchangeable". Then he moves on to explain that "the key [to determining if something is interchangeable] was that the hardware was different ... and more modern software could not be loaded ... and run without error." In other words, if the code doesn't run on the old hardware, then it's not interchangeable and therefore not prior art.
Then, in one of the paragraphs that you brought in, he indicates that he's summarizing and repeat ("the 40,000 foot-level"). He says that the "methodology" was different. Here he uses "method" or "methodology" to mean code. You can see this in this quote from elsewhere in the interview: "when we looked at the source code - I was able to read source code - I showed the jurors that the two methods in software were not the same" and this one: "you couldn't load the new software methodology in the old system and expect that it was going to work". So again, he's saying that if you can't load the new code on the old machine, you don't have prior art.
It appears to me, from your quote and from the article, that he believes that running new code on an old device is "the key" to determining prior art. Is this the informed position you're talking about?
Multiple times in this thread and others, you link to a list of large government contracting companies: http://washingtontechnology.com/toplists/top-100-lists/2011....
And then, a long time ago, you linked to a dice posting in order to ridicule it:
http://news.ycombinator.com/item?id=3072172
> 5 years experience with SQL Server 2008
> http://seeker.dice.com/jobsearch/servlet/JobSearch?op=302...
If your job is as bad as you seem to imply, then I certainly hope you heed people's advice and find another. But I'm beginning to suspect that you're being intentionally misleading for some other purpose.
A glance at your comment history reveals a pattern: anecdotal examples of wildly low salaries ($40k-$50k), and unsubstantiated claims that every possible source of salary data (aside from your examples) is inaccurate.
Just a couple of examples:
http://news.ycombinator.com/item?id=3978058
>That's worse than the OP's link.
>If any company paid that much there'd be a line at the front door every single day of people wanting to be hired.
http://news.ycombinator.com/item?id=3953590
>You're "facts" are far from that.
>The developers we have onsite with the customer (Department of Defense with Top Secret clearances) are paid roughly $40-50K/yr USD.
>If there were companies that actually paid the salaries you're quoting there would be a line of people at the front door every morning wanting to get hired.
http://news.ycombinator.com/item?id=3959410
>Your reference is like citing Ms Cleo - pathetic actually.
>If companies actually paid those amounts listed there'd be a line of applicants at the front door every single morning wanted the job.
http://news.ycombinator.com/item?id=3344467
>If there were developer jobs paying that much, there'd be a line of people at the front door every day wanting to get hired.
>Quality people are easy to find, a quality company is not.
Where do you live? I found the 'cursing' to be totally natural.
Working on a very young lean startup and as we've gotten off the ground we've struggled with these problems. We'd ask what they were looking for and we heard about big integrated solutions and lots of little (low value?) features. It didn't seem like this was leading us in a lean direction at all.
What we ended up finding much more valuable was to identify specific hypotheses about the problem we were trying to solve. And then set up a specific "experiment" to test our hypothesis.
An example would be helpful: our original idea was that we would make a system for collecting conference session evaluations -- replace the paper eval forms with a web/smartphone based version. We identified conference organizers as our market. Thus our first hypothesis to test was, conference organizers care about collecting session feedback.
We called and emailed a bunch of conference organizers with a really quick questionaire: do you collect feedback? how? what do you do with it? how much do you spend on it?
That's it. At the end of 10 responses, it was totally clear that we were barking up the wrong tree. Pivot.
I was one of those hackers that stuck with Apple through the 90s. In 1996 I learned how to install netBSD on my mac and in 1997 I installed MkLinux (an Apple sponsored project). I was incredibly excited when Apple announced that it was going to integrate this new (to me) exciting world into the next generation of their operating system. In 2001 I finally got my first machine that was powerful enough to run OSX. But I was a little disappointed. There was no native software, my OS 9 software barely worked and the thing kept breaking. When two power cords broke, the screen broke and the disk drive crashed, I traded for a ThinkPad.
Especially amongst all the repetitive articles about software patents, bitcoins and google+. Don't get me wrong, I think all those things are interesting hacker news, I was just trying to add diversity.