628 karma · joined August 19, 2013
Sounds like they have perfectly valid concerns, actually.
When it comes to protecting restricted (and potentially rather damaging information) -- which also happens to be the University's property, anyway -- it's generally prudent to suppress the source, and ask questions later. Taken out of context, even a single vindictive or poorly composed review can be fatal to an instructor's career. Failing to take action to suppress their unauthorized distribution can also invite nasty lawsuits.
So this doesn't seem to be about "the man" stepping in and quashing student creativity and initiative (as much as some may prefer that narrative). If anything it seems that Yale did the right thing, in this case.
I mean, yeah, you made a line graph and such. And you cite mysteriously precise figures like $22731 and $23706. But to conclude that people with net expenditures in these brackets who also aren't presently working just aren't looking (let alone that they just don't want to work) requires a far deeper (multi-factor) analysis than you're making.
It's also very hard to reconcile with the sheer length of the waiting lines at some of the daily employment agencies I've seen at 6AM in my own neighborhood. Or the utterly dour, resigned expressions sewn into the faces of some of the long-term unemployed that I'm sharing seating space with at this coffeeshop, right now.
I know that observation carries no statistical weight; but it's meant to be illustrative -- if you're going to make sweeping generalizations about a class of people that contradict the day-to-day observations that most of the people reading this thread seem to have about this topic -- and which are also, BTW, rather insulting to the intelligence and character of this class of people -- you're going to have to be a lot more rigorous in arguments you're offering.
Everyone knows (or ought to know) that the value of most of those perks has to be offset against something in the company's budget. (Namely: your paycheck[1]).
(New) startups shouldn't try to compete 1-1 with the handful of already stupendously successful startups on these items.
Far better to offer something the big boys can't: like actual responsibility (the kind that by definition, always comes with the act of taking on substantial risk); real challenge; and an opportunity (and expectation) to not only see, but contribute strategically to the whole picture -- including things like business strategy, shaping the company's hiring & general social culture, etc. Not to mention things like decent office space, lack of bureaucracy that's inevitable in any large organization, etc.
Those are what I call real perks -- not free massages, a treacly beer keg, or mediocre sushi (half price after 4p!)
[1] Actual benefits, like health insurance and paid training, are an entirely different matter of course. In these areas, the employer contribution (at scale) has a decisive leveraging benefit (i.e. generally providing more than what the employer could for herself out of pocket, dollar for dollar). But most of these fashionable "perks" out in startupland have dubious benefit at best -- and most of them I'd happily trade for the (implicit) negative offset in walking around money that goes with them.
In NYC (during the Occupy days), those mirrors would have been swiftly confiscated as "potential weapons."
You haven't answered any of the main counterpoints people have been raising to your rant so far. Trying to distract us with academic gobbledygook really isn't helping your case.
It's just as in academic research -- yeah, maybe it's buried in the source somewhere, but no one has time to parse paragraphs, and divide numbers for you -- especially when you're already trying their patience by making such structurally weak arguments in the first place.
Pointing fingers (and, implicitly, accusing people of being lazy or unable to read) to distract from the fact that don't seem to have an answer for their main criticisms of your "argument" doesn't help, either. It's just grasping at straws.
Weird, huh? Anyway, since I couldn't readily find substantiation for that 24% number, and the added dubiosity coming from the fact that he doesn't even mention whether it's adjusted for students, disabled, etc (as is standard practice in econometrics), I didn't even bother with the other charts or arguments he was trying to make.
It’s a fairly pervasive myth within the US that the poor work very hard at unpleasant jobs. But this is nothing but a myth - according to the BLS report A profile of the working poor, 2009, as of 2009, only 24% of people below the poverty line were in the labor force (this means working or looking for work) for at least 27 weeks/year.
Even if one knew where in the BLS report to dig for that 24 percent figure (and independent of the fact that the author doesn't even mention whether it was was adjusted for traditional non-working categories -- e.g.. students, seniors, disabled, in or recently out of detention -- or not, as is standard practice when talking about unemployment numbers) there are so many plainly illogical (and just plain weird) assertions jumping out of this rant that you kind of have to wonder why he bothered.
For starters: that
"below the poverty line" === "poor in the U.S."
or, my favorite: "in the work force at the moment" === "willing to work in general."
Really now?OTOH Perl people tend to like the way we can, for example, create histograms (and nested structures like graphs) a bit more fluently with autovivifying hashes, e.g.:
my %a;
for my $x (@x) { $a{$x}++ }
than if we always had to be saying if (exists $a{$x}) {
$a{$x}++
}
else {
$a{$x} = 0
}
Or as Perlistas would be more prone to write (if forced to use a non-vivifying hash): exists $a{$x} ? $a{$x}++ : { $a{$x} = 0 }
Or gosh, who knows: $a{$x} = exists $a{$x} ? $a{$x}+1 : 0
Or to have sat around and waited for 10 years or so until Hash::Util was invented (after Perl 4's initial release), provided then you knew to look for it, and how), at which point you'd finally be able to say: use Hash::Util 'unlock_keys';
But as it happens, when Perl 4 first came out, autovivification (and its cohort, promiscuous ducktyping) were chosen as the default behavior for many of the language's core constructs (not just hashes and arrays). It's just the way Perl rolls. Whether it's the "right" tradeoff to make or not, from a socio-engineering perspective, is an interesting question (and partially a matter of taste). But in general Perl has been pretty consistent in its approach to tradeoffs like these.That's why you see food trucks offering tacos, sushi, or organic chocolate-and-truffle-oil-suffused hempseed brownies, respectively... but food trucks offering all 3 of these, not so often.
With recruiting it's kind of the same. Also, out-of-towners have different filtering / recommendation / communication needs, and take different payscales, also
So they're probably just applying the 80-20 rule, and catering to what their known client base seems to ask for most.
Next up: the idea that the notions of Monad, Functor, and Category (in whatever guise) are even needed or helpful to do strong FP.
Definitely not a place I'd think to go looking for available talent, in any case.
If so, then evidently they're the kind of company that seems way, way more concerned with employees who get "emotional" about discriminatory practices... then about the discriminatory practices themselves.
The point as I understood was that for all of PHP's faults, (almost by accident) it managed to get certain things right, or at least right for the Web in the time in the time of it's heyday.
These being, chiefly, that the much-maligned document-based scripting model turns out to be really easy to package, deploy, and most of all, to learn. And that it also (again by accident) happens to be in some ways easier to program safely in, compared to handler-response based frameworks.
Don't get me wrong -- I don't see these as anywhere close to redeeming strengths for PHP. It's still a crappy language, all the cheerleading and apologetics from the likes of FB and Etsy notwithstanding. But the presentation does make some interesting points.
It's not about the Irish guy, or the Indian guy.
EDIT: for "internal allocation", above.
May or may not have been, but sounds like you didn't even read the article, judging from your response.
Hint: It definitely was not about a $10k salary difference.
Well, actually, I would. Because (being as it seems to keep happening, over and over again, in big companies and in small companies) clearly it's not the mistake of a single individual. The fault lies with the mindset of those who create the hiring culture in the company at large.
And the shabby treatment frequently dealt out to candidates may not be entirely consciously intended, but still, it is no "mistake." It is a perfectly predictable outcome of the hiring culture in these companies.
See also:
It's someone very high up in the Amazon food chain, responsible for failing to create a hiring process that emphasizes the need to treat candidates respectfully at all stages of the process.
And that means, for every candidate, having one person take ownership of the communication, start to finish (regardless of the outcome). You now -- "be respectful, be kind. And always, always close the loop."
It's like, really, really simple. But somehow Amazon and so many other companies seem incapable of wrapping their organizational heads around it.
What's interesting is that the poster above simply keeps asserting, over and over, that it was "because of the mold, ya know" as if the surprise incineration was an obvious, necessary result of the situation. Clearly it wasn't.
So maybe the real story should be "why no one wants to talk to recruiters anymore, no matter who they're hiring for, or how much they're offering."
Hate to break this to you, but Congress created the SEC.
You also might want to look into Articles 1 and 8 of the Constitution, BTW.
The "mold threat" argument is so utterly vacuous -- it's hard to imagine that anyone making it can really be taking themselves seriously. And this pooh-poohing of the documents as being merely "cool" reflects a staggering degree of ignorance about the value of primary documents in historical (and legal) research.
At the same time... it's not hard to imagine county bureaucrats thinking pretty much exactly in these terms. "Wha, a buncha photographs? Old title papers? Whoze goona be innersted in that? Someones gonna get SICK from all that ICKY mold and we might get SUED!"
Yep -- that must have been exactly what they were thinking.