277 karma · joined August 17, 2011
This article also fails to mention if the study controlled for types of law practiced by these people -- something that still persists in our "pay gap myth." A lot of the PoC and women that I know in law started out doing basically volunteer work, contract review, innocence project, public defender and environmental defense work, etc. While a lot of the white men went into patent law, divorce law, corporate law, etc. Basically higher-paying professions.
[1]: My bet's on people who can barely use a computer stood up a wordpress or joomla site, and only really understands how to edit configs, not actually change the programming.
This is why any economic recovery plans that don't focus on growing the income of middle- and lower-class americans is doomed to fail. The rich can already buy anything they want, and they're saving like crazy. Until we unleash more demand from the lower- and middle-class, all efforts are futile.
It's also why we should be focusing on, and supporting, raises in the minimum wage, reductions in work weeks (more demand for leisure goods and services), and decreased tax burden on the middle class.
This necessarily implies a (potentially dramatic) increase in taxes on the wealthy. They can afford it. If someone claims they'll cut and run to a tax haven country -- let them. We'll do better without them around.
If you have kept up versions as I have, it's practically no different. If this means we get features sooner rather than waiting for a whole major version upgrade, I'm happy.
Yes, Adobe had a big clusterfuck when they did it, but you know who hasn't had as big of one? Microsoft Office. I subscribe to their office 365. 10 bucks a month for 5 computers, the whole office suite. I'll happily pay that.
And besides, there's always the community edition if for some reason your 120k/yr job doesn't let you afford 100 bucks per year...
People just have a meltdown anytime anything changes... chill the fuck out for a few minutes and let's see what happens.
Your brain needs time to absorb, process, and synthesize. It can't do that if you're trying to force-feed it new information faster than it can handle.
Take some time to write a couple tests against the code, to make some small refactorings, etc. If you still feel overwhelmed or underwater, talk with your manager and just tell them the code is a pile of crap (if it really is). They don't want to hear it, but they might cut you some slack.
This is a dumb example.
Her and I could be friends.
For example, how do you evalute postfix addition? If you have v1.0.0-alpha3 and v1.0.0-alpha10, are all semver implementations supposed to do an alphabetical check until it sees a string? Or should you zero-pad anything with text postfixes? And how do you deal with labeling branches or architectures?
Internally, we no longer use semver, we use the build number as the version, and the commit hash as the input to the deploy systems.
It was remarkably simple to set up, a bit harder to tune, but we ended up getting something like 5000 req/sec at <= 10ms per query sustained for several hours.
I'd highly recommend learning neo4j, if for nothing but the paradigm shift it forces you to learn.
Even if it was a bunch of racist/misogynist people, you have to consider that despite the messenger, the message might be valid. That's what being open-minded means.
Basically reddit was a cesspool of villainy for a while, and now she's turning it into a cesspool of SJW/"Mod-approved language". I'll take the former any day of the week. When you're afraid to speak your mind because you might get shadowbanned or a mod of a subreddit you never visit might be offended at your comment and complain to the admins, it's just a way to stifle speech.
It's basically GamerGate expanding into social media.
1. IDEs are not a crutch. They're a useful tool. Anyone who talks about expressiveness or efficiency in Ruby but discounts IDE help is a hypocrite. You learn the tools you have. Refactoring large methods, extracting interfaces, mass renaming with guaranteed safety -- those things actually matter when you learn to use them.
2. Ant is dead. Hibernate is dying. Spring XML config is largely dead. Much like the perf argument, most of the bad impressions people have of it are based on years-old issues.
3. Tools like Spring Boot and Dropwizard have made it so a Java REST service is smaller than a RoR one.
4. Gem upgrades can be backwards incompatible, so once your app is of a certain size, your framework support becomes very rigid and brittle.
5. Twitter left Ruby because of perf issues. drops mic
6. Active Record ~= Hibernate. Hibernate can be configured with annotations, so leave the XML out of this. You still have n+1 and over-selection of fields by default.
7. Global interpreter lock. 'Nuff said.
8. The actual argument used by DHH wrt performance was, 'Ruby is fast enough' -- if the Java community tried that, it would be an endless mocking parade.
I could go on, but won't. I don't care if others leave Java, just means more work for me. Hell, replacing shitty rails apps and replacing them with reasonable java apps is a good consulting business :)
It's a good parable, but doesn't stand up to too much scrutiny.