I'm bowing out of this discussion. Things have gotten far too polarized and
nit-picky.
However, I still feel it is worthwhile to at least chime in one more time
because I think some of the points raised here leave developers with wrong
and dangerous information. The overall opinion that you don't
One thing I'm gonna add.
A contractor we once hired submitted code with a copyright notice on
it, to a 3rd party developer. That contractor's contract was terminated
immediately.
Doug McCune wrote:
I'm bowing out of this discussion. Things have gotten far too
polarized and nit-picky.
Alen,
You are either being intentionally obtuse or being incredibly wittyI'm just
not seeing the humor or the usefulness of your comments
GB,
Bubba
From: b_alen
Sent: Thursday, June 12, 2008 7:44 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: OOP and Work for Hire
You
I've stayed away from this conversation because I agree with Doug that this
conversation has been kind of intense and in some cases borderline
ridiculous. But if he's bowing out I have to speak up and say he has been
correct on almost everything.
To OVERSIMPLIFY: Copyright protects code.
No argument there, however that employee cannot work on the other
employers floor w/ the same equipment provided by the first employer.
b_alen wrote:
No, the floor is not Employee's. But if the employee by doing the
finishing of the floor realizes how to do it with different tools and
and are proficient at, then
using the proceeds to behave like a twisted, salted pretzel with your
significant other...
GB,
Bubba
From: b_alen
Sent: Wednesday, June 11, 2008 3:31 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: OOP and Work for Hire
No, the floor is not Employee's
:32 PM
Subject: [flexcoders] Re: OOP and Work for Hire
Definitely not with equipment, that would be called theft. But with
the knowledge gained yes.
The question here wasn't could I take the code of the company and use
it, but could I use the code (i.e. knowledge) that I have developed
It really depends on what that knowledge is. ;)
b_alen wrote:
Definitely not with equipment, that would be called theft. But with
the knowledge gained yes.
The question here wasn't could I take the code of the company and use
it, but could I use the code (i.e. knowledge) that I have
significant other...
GB,
Bubba
From: b_alen
Sent: Wednesday, June 11, 2008 3:31 AM
To: flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com
Subject: [flexcoders] Re: OOP and Work for Hire
No, the floor is not Employee's. But if the employee by doing the
finishing of the floor
as domestically. I've
no problem of agreeing to disagree, but I do ask that you let me know your
particulars so I can avoid doing business with you... :-o
GB,
Bubba
From: b_alen
Sent: Wednesday, June 11, 2008 8:43 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: OOP and Work for Hire
So
Jeffry Houser wrote:
It really depends on what that knowledge is.
That's really key. Let me give you a real-world example involving code,
rather than hardwood floors and toothbrushes ;-)
I've specialized in localization and internationalization for 15-20 years.
I'm bilingual, so that
Subject: RE: [flexcoders] Re: OOP and Work for Hire
Jeffry Houser wrote:
It really depends on what that knowledge is.
That's really key. Let me give you a real-world example involving code,
rather than hardwood floors and toothbrushes ;-)
I've specialized in localization
Typed code is what you are paid to deliver. That is what the client is
buying. When the client pays you you are selling those digital lines of
code.
I just wrote a book for wiley. I cannot copy and paste any of the prose that
I wrote and post it on my blog. It belongs to wiley. I sold it to them
The company that you worked for has the right to patent the implementation
of that great algorithm that you came up with. So if that's really an
inventive algorithm then yeah, they have the right to use it and you do
not. In the real world is this how things play out? often no, but I'm just
trying
: OOP and Work for Hire
So if I create a great algorithm for collision detection while working
for a client I can not use it ever again? And if I have to make it for
10 different clients in a year, I have to create 10 completely
different solutions for the same problem, so I don't copy. First
b_alen wrote:
So if I create a great algorithm for collision detection while working
for a client I can not use it ever again?
Algorithm, you can probably use it again. It depends how obvious or
unique it is. In theory, algorithms / approaches to solving problems
are not patentable.
What if you spin it as a PR opportunity for the company, and ask to be able
to use the code you write as the basis for explanatory tutorials, without
giving away any company-specific trade secrets, and give credit to the
company for contributing the code? Could be a win-win for everyone involved.
Subject: [flexcoders] Re: OOP and Work for Hire
--- In flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com ,
[EMAIL PROTECTED] wrote:
Maybe. If said tools and techniques are uncovered while being paid to
accomplish this floor re-finishing, then No they do not have any
legal right to re
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: OOP and Work for Hire
--- In flexcoders@yahoogroups.com, Doug McCune [EMAIL PROTECTED] wrote:
Typed code is what you are paid to deliver. That is what the client
is
buying. When the client pays you you are selling those digital
lines of
code
The company is buying the code that you write. They are not buying your
time. They might pay you based on how long it takes you to write the code,
but in the end all they care about is owning that code. If they pay you
$10,000 to write code, and then you turn around to another company and bid
on a
As an aside, I would never sign such an agreement separate from a
project / consulting contract; and have turned down clients who asked me to.
If they aren't going to award you the bid, why would you sign such a
document?
Amy wrote:
--- In flexcoders@yahoogroups.com
for this project is
also looking to obtain a competitive advantage, soyour sharing of
information outside of the employing company would be counter to their desired
end game
GB,
Bubba
From: Amy
Sent: Tuesday, June 10, 2008 6:00 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: OOP
BTW, I think you need to re-consider your definition of OOP.it has
absolutely nothing to do with maintaining IP.
GB,
Bubba
From: b_alen
Sent: Tuesday, June 10, 2008 10:45 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: OOP and Work for Hire
BOLLOCKS!! Of course you can
23 matches
Mail list logo
