HN user

heathkit

35 karma
Posts1
Comments17
View on HN

The best part is, 15% of GitHub's employees are women, and only 6 of them are developers. So you could actually do a really accurate survey with a small sample size!

That actually sounds extremely plausible to me. I mean, I don't think the guy literally said to himself "she won't fuck me, revert!"

What I imagine happened is some guy at work had a crush on her and made an awkward pass at her. Maybe he tried to smell her hair or something, I don't know. She shot him down, then he got all butthurt and started undoing her commits on the projects they worked on together. Because they were painful reminders of her.

From his perspective, he's a sensitive guy who just got rejected and isn't coping well. But to her, he's the guy deleting her code because she wouldn't fuck him.

That doesn't seem crazy at all to me. It seems totally possible, and just the kind of situation competent HR departments are supposed to prevent and mitigate.

I think this is the crux of why G+ failed. When I first started using it, circles seemed like a killer feature. I divided all my contacts into work, friends, family, by location, etc. So I could share programming stuff with tech friends, but local stuff with local friends.

But, instead, I find I just share everything I care to share public. I think what people share is part of how they present themselves, and if I'm always in the context of being myself, with my real name and the same picture, then I'm going to share the same set of stuff.

Maybe I'm biased, but to me the story of RIM is another example of the triumph of open source over closed-source solutions. iOS is based on BSD, Android on linux (and heavily leverages the OpenBinder IPC mechanism. I've looked closely at the old blackberry OS and the new QNX based one, and it's amazing how far behind they are.

Seeing the new QNX OS and how they're using it was a real eye opener. They have nothing that even comes close to the features of ICS on their roadmap, and they just don't have the resources or expertise to ever catch up.

I agree, they do make good hardware. But the software side of their house is in the stone age, and the recent acquisitions haven't really helped at all.

It seems like I get calls from recruiters every other week looking for people with Grails experience.

I used Grails for a project four years ago - I think it made a lot of sense then. We wanted a simple web UI for something that needed to deeply integrate with some java libraries. We had just done a relatively simple UI with Spring and it was pretty amazing how much better it was to work in Groovy.

However, these days I don't see why anyone would pick Grails over Rails. You can deploy rails on the jvm just fine, and it's much more mature. There are tons of tutorials and example code out there.

It's not a performance thing - it's just that ruby/rails is pretty mature now and runs on the JVM very well.

The problem isn't that developers "expect" this stuff to be free. It's that the quality of a particular development platform is related to how many people are using it - how many tutorials are there out there, how much sample code, how many libraries, etc.

There may be some social bias against paying for stuff, I think partially because people got burned with vendor lock-in. Technology changes so quickly, it's hard to know what a tool is worth before the fact.

But there's also a very real economic reality at play here. The most valuable platforms will be the ones with the most people collaborating on them, and that's always going to be the free or open platforms.

As you move up the infrastructure chain, I think people are more willing to pay for useful libraries or services, especially for ancillary stuff. But what rational person would build their business on something they didn't own?

Yeah I got tubgirl.

Welcome to the internet, guys. If you have a public place that displays user generated content, it's going to be flooded with the most vile images around.

Since we've already had goatse and tubgirl, I'm guessing the next is lemon party.

My first job was at a company that I'd say was much, much worse than Amazon. Smaller, no real engineering practices, and they'd just chew through developers paying them as little as possible. Yet they made money!

I was migrating a legacy system to a new platform and we got a call from an irate customer. Apparently, he had just paid us last week but now his account was shut off. The odd thing was, no one I talked to even knew what product he was talking about, or what website he was on. I checked with our payments person, and he had sent us a check, but no one knew what it was for! Eventually I tracked it down to some legacy discontinued product that had been handed off between three successive engineers who left the company, then forgotten.

You don't have to treat your employees well, or even make a good product, to be successful. You just have to get people to give you money.

Whenever people ask me if they should work at Amazon, I always say maybe in AWS, but never in anything to do with the retail website. I'm glad I did it, I certainly learned a great deal, but whenever a recruiter from Amazon calls these days I just laugh in their face.

Also, when I left two years ago they weren't using AWS for anything internally. S3 got a lot of use, but anything considered essential to keeping the site up had to run on real hardware.

That first month after I quit, it was such an amazing feeling not to have to go on call. I agree, never take a pager unless it's an essential part of your job.