"In practice it's simple - if you're paid to build a thing for someone, that someone owns the thing. It's known as a "work for hire". That's what your customer will expect, anyway. I mean, would you pay someone to build a thing for you and think didn't own the copyright on the thing?"
I don't think that this is true, at least in the US; the default is not work-for-hire, the default is that creators own works. While it is possible that I'm mistaken, I'd imagine that it is jus the case that you're generally working in situations where it isn't an issue (for instance, you don't want to reuse the code, the folks you're working with don't specifically care, or something).
I don't think that this is true, at least in the US; the default is not work-for-hire, the default is that creators own works. While it is possible that I'm mistaken, I'd imagine that it is jus the case that you're generally working in situations where it isn't an issue (for instance, you don't want to reuse the code, the folks you're working with don't specifically care, or something).
Otherwise, I agree with you.