Nations aren't people. If you're a nation, you read even your allies' mail.
2,946 karma · joined October 29, 2011
Security researcher residing in New York.
Nations aren't people. If you're a nation, you read even your allies' mail.
You ignored the majority of the parent's point, instead electing to pick on one word ("Romans") and then strawman that half to hell.
If it pleases you, and you'll read the rest of his argument before bashing out an angry rebuttal, put in some other example of your choosing.
You literally missed his entire point about the purpose and necessity of intelligence gathering agencies in the global theater. People shouldn't have to worry about their exact word usage because someone -- like you -- will come along and nitpick it so the original point is buried under the burden of a disagreeable example.
You responded to his post either without really reading all of it or understanding it. Allow me to summarize his point:
Spying does not require nor dictate that two countries are enemies. Allies and spying are not mutually exclusive - your entire point about how you'd like to think about your allies as someone from the Netherlands is thus irrelevant.
Next, allow me to address your second paragraph. All states are always competing. We don't live in an idealistic world where globalization has renderd us kumbayah with everyone else. Again, let me reiterate - that does not mean we are enemies.
Finally, or course there is an economic benefit to all intelligence gathering agencies. This should be self-evident. But no, that's not the only one by any means. Intelligence gathering agencies also benefit their homelands with intelligence, which is obviously not just an economic benefit.
It would be rogue if it decided to, say, give crucial information to a foreign country at the expense of the United States.
He made a point about whether you'd work with a team again, and how this is all that matters.
You made a point about whether it'd be good for the company for you to work with people you think are nice and can hang out with.
That's not at all the same thing. You're not countering what he said. He's talking about actually working and getting things done, and how productive your team is as a functional unit. You're talking about how much you like your team.
It's implicit in "would I work with this team again" that you'd be trying to work with the team and not just hang out for a beer or five.
Some of the best people I've worked with, and people I'd work with again, are people I don't personally like. But if they're productive and we have good professional chemistry, I don't need them to think Aaron Rodgers is the best quaterback to work with me.
The takeaway is this: you can work with a team and be extremely productive together, but you don't have to desire working with them again because they're nice or you like them. You should desire to work with them again because they're awesome and complement you well professionally.
It doesn't matter if you think the movies are crap - the "art of narrative storytelling" isn't mutually exclusive with shallow film making. It's a technical expertise with developing a story/dialogue/scene sequence. The literal story can be shallow and unappealing, but the story's visuals, acting, etc. are all highly tuned.
I also don't agree that "works of art" are what keep Hollywood profitable. You just said most movies are terrible and formulaic. Those are the biggest money makers, unless you call those more artistic than the indie films everybody loves.
You go on to compare Hollywood to the typewriter. The typewriter is an extremely poor analogy. It was literally eclipsed by superior technology and made obsolete.
You cannot make Hollywood "obsolete" - there is a worship culture to celebrities, a direct product of Hollywood (as the author describes). Hollywood survived the television being put into homes, which would arguably be more of a technology progression. You can't just beat a cult of personality with technology is the author's point - Silicon Valley isn't going to remove something so deeply embedded in America just by getting "smarter" about it. It's vastly more complex than that, and it's not going away just because a startup comes out with something that attempts to make Hollywood "obsolete."
I'm not saying it can't be done, just that your argument doesn't work.
"Your A/B test demonstrates it's better for you in the short term. Great! Now you're just being dishonest, instead of ineffective and dishonest."
EDIT: That probably sounds harsh. I have nothing against YC companies, this advertising is just something I personally find disagreeable and annoying.
Bloated features are what you just described - more often than not, it's unproductive to code in extra things you don't need on a deadline. You can better work elsewhere. And yet, I think you're right, a lot of developers who will eventually need/want what they're putting in later anyway.
On the other hand, YAGNI has significant security implications. I posted a example downthread about how a database could be compromised by adding in a back-end feature for lazy admins. In that case, YAGNI is really something you want to avoid.
A lean system is an easier system to plug up. But I also understand that's a bit outside the scope of strict features.
I'll bite: it's really terrible for security purposes. Aside from the typical YAGNI feature examples, there's plenty for application maintenance and back-end development.
Let's say you have a database with several layers of privileges. You frequently have to perform actions that require higher privileges than that user has, and you're a lazy dev. So you try to automate this process by adding further code to your system design, expediating the entire process at the cost of some authentication.
Bam, huge red flag and a half. Yes, you can have this and defend it at the same time, but in most cases, it's silly to try. Adding code just adds another vector and a half.
That said, yes of course adding features you don't need will bloat the system. But that pet example kinda sucked, I'm sorry.
A really good format would be, as another commenter said:
{YC Company} {Season Number} is looking for {Job Title}. Join us!
Bam. Doesn't that just look better? Sexier? More appealing and respectful? You don't have to be 25+ to get that, it just has to be introduced.
So, now that it's the top story on HN, and has been introduced, let's maybe try to codify it for future job postings?
Common objections:
But we're young and hip, we wanna look different from the big companies! - Doesn't matter. Still bad practice.
But we don't like labels. We want generalists. - Then specify that. Asking for a "ninja" or some other nondescript title is retarded.
But we want to say what we do! - That's what the post is for.
YC companies have the exclusive ability to post job ads on the front page. I highly doubt there's any reasonable justification for posting anything aside from a standard template. It's not like you need more help.
I would have rather had a more fleshed out point about people and a sentence about how the author is a problem solver than so much about what he can do and then some stuff about other people.
Other than that...I'm not sure what else to comment. Of course you can't fix people. If we could, we'd live in a utopia where everyone was happy and operated efficiently.
On a serious note, it probably worked. This might come across as sexist, but aren't we as men more easily "gamed" when it comes to dating? We are very visually oriented...more so than females.
That's not actually achieving anything. It's just more complicated term usage because you don't think the word can be used positively.
It's all semantics. I think the author was very clear and the whole concept made sense to me despite the use of the word "faking"...it didn't bother me at all.
I guess it's semantics.
[1]: http://news.yahoo.com/blogs/nightline-fix-abc-news/why-texas...
And what the other commenter said is also true. Most people can't even tell a difference in color. If you serve white wine dyed red, people describe it as they would red wine, and vice versa.
EDIT: Citations:
[1]: http://en.wikipedia.org/wiki/Wine_tasting#Blind_tasting
[2]: http://www.theguardian.com/lifeandstyle/2013/jun/23/wine-tas...
[3]: http://ageconsearch.umn.edu/handle/37328
[4]: http://www.yumsugar.com/Wine-World-Reels-2-Buck-Chuck-Wins-A... (not a citation in the strict sense, but a demonstrative reference)
For the curious, it's true, most people can't tell the difference between cheap and expensive wine[1].
[1]: http://www.theguardian.com/science/2011/apr/14/expensive-win...
On the other hand, this sort of humor emerges even in high school among guys. If a group of bankers not very connected to him hear about it, I could see a joke like that beinf said. But the same could be said of any profession. That's humanity for ya.
Not that I'm saying they're all like that. But they're not all arrogant or cynical. Maybe workaholics.
It's unfair to stereotype bankers this way. You could find books that similarly portray politicians, lawyers, etc. I know a few bankers and they're not like that at all. It's a mixed bag.
I've also heard far worse jokes in the kitchen of a restaurant. You want to be offended? Thems' a good place to start.
He was careless. Most teenagers are. He was probably not even seriously thinking when he said it. He's almost 30 now. Let's judge the man on what he says today.
I'm assuming you've never met Mark Zuckerberg. All you have to go on are his portrayals in the media.
Have you ever said anything racist? Sexist? Discriminatory, widely insulting? Have you ever joked about things you would do to take advantage of other people?
How would you feel if any one of those things were held against you by everyone years later? I've personally said worse things, and I've later regretted them. I'd be mortifed to have them follow me for a decade. The man is turning 30 soon. It was literally a decade ago. Let it go.