Philip wrote:
> Shane wrote:
>
>> Mercury wrote:
>>
>>>> Heh thanks,
>>>> I could do with the job, its SA and I wouldnt mind a little piece of
>>>> paper saying Im not as bad as I smell/look
>>>
>>> Can't smell anything here. Oh and **** your gorgious.
>>>
>>
>> With talk like that, you could buy me beer 
>>
>>>> The hours are *perfect* for me, I could do with the dosh (what
>>>> struggling
>>>> student couldnt)
>>>> I'll be sitting on my duff working remotely for the job, which is
>>>> *another*
>>>> plus
>>>> Its servicing clients so I will be dealing with them on a day 2 day
>>>> basis
>>>> (well as day 2 day as a p/t job can be)
>>>> Im now beginning to think Im just moaning over details 
>>>> The PEs first lang is english, but hes also fluent in comp.lang.java
>>>> Which means he *should* be used to dealing with IT staff
>>>> (Is it IT, ICT, or ISS staff now???)
>>>> Maybe hes being flippant because it was fairly obvious (to him) how he
>>>> wanted it, and thats precisely the type of answer Id give.. socially..
>>>> but not professionally
>>>> Hmm
>>>
>>> Negotiate on the points that stick - 12 months is a bit much for a SA /
>>> part time position (if their grasp on their clients is so feeble, then
>>> they have an issue and need to sort it) - perhaps suggest a sliding
>>> scale.
>>> 2 weeks per month employed limited to six months. Six months is still a
>>> lot IMHO unless they are specific about the technology / proprietary
>>> nature EG they are working on a something to be patented, then it
>>> would be
>>> reasonable for a long period.
>>
>>
>> This is good advice
>> Thanks
>> Although the IP details are very reasonable compared to other
>> contracts Ive
>> seen (Basically all hes interested in is the copyright of things produced
>> for him
OK, but what about if you base some of the work on stuff you previously
did? say use a piece of neat java code you have developed over the last
year? You would not want to lose the right to continue using it would
you? I'd discuss this point.
>> Damn I *hate* contracts, I can see the point when employers have to cover
>> their ass, and it covers employees asses as well... sometimes... but I'll
>> never like them... least not till I get the nice brunette in the LLB
>> course
>> up the duff....
>>
>>
> You do it on company time, it belongs to the company & you can't take it
> with you when you leave (without their say so)
>
> You do it on private time in a different field, it's yours.
Depends on the contract, some say all IP. So if you are a techy in IT
and say develope a world beating combusion engine in your own time, you
might find them coming after you as its worth their while.
In 2000 I went to work for a hospital on a contract, they tried this
one, I crossed those out in front of HR. This was for 2 reasons, it
covered all IP, even in un-related work, plus the output I was giving
them was based on taking thier raw data putting into my "middle work"
with the output going to them....they wanted all IP to be handed over to
them and specifically not re-used incl the middle process. We
negoitiated a new contract on more reasonable terms and off we went.
This happened again with a big American Company, they wanted all IP, but
this time it was wrapped up in an "ethics" clause that they expected us
to sign about 2 years after I started and every year afterwards, I
refused. We had an argument, they claimed that what I was doing was
signing to say I had read it and not that I agreed with it, but that was
not what it said from what I read. This was an ongoing drama til I left....
So you do need to be careful.
> You do it on private time using company IP, specialist knowledge or just
> in the same field as the company, you have a debate that you might not
> win. But if you improve the company's product on your own time I'd
> reckon you are entitled to reward.
>
> Philip
>
> (
regards
Thing