Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Dear Tilly,

How horrible to hear about your difficulties with your employer. My heart goes out to you. Know that we are all behind you whatever you decide.

IANAL, but it seems there must be some reasonable limit to what your employers can claim. Obviously they do not own your every utterance, and code written to be illustrative in an online discussion I would think is part of the code as speech thing. Programmers socialize by writing code to each other. Perhaps you can make a list of all of your past work and which ones your company finds threatening to its business. A list of meetings with date/time/participants when your open source work was discussed would be very useful. You don't get brownie points for a pyrrhic victory, best to keep emotion far away and rely on professional advice.

Despite my own anger at hearing this, my guess though is that getting them to reduce their demands and then buckling under what's left is going to get this finished the most quickly. I hope they will relinquish demands on your your open source work, which of course they can still use according to the open source liscenses or perhaps license from you in some way.

But the most important thing is to get your personal situation stabilized and take care of your family, as you have pointed out. Having gotten myself screwed (more than once) I have generally found that getting out of a situation and starting over is more satisyfing, and more lucrative, and that the main problem is sticking in the same place under a capricious evil-minded boss. I don't know if it is possible for you but as soon as I got out of one bad situation I made in two months double what I had made the previous six. You are going to come out of this stronger in some way, but get out of it as soon as possible. You won't be as productive or clear-headed for your work or family if you feel like you are ekeing out days in the dungeon. Your employer must also understand that it is killing the goose (a smart, creative, overtime worker!! egads!!) that lays the golden eggs. They soon will, as soon as you stop helping them cover up their complete lack of brains.

Good luck Tilly. Whatever you choose we're behind you. Hope you get life back in order Asap, love your wife, have a couple beers, and come back to tell us about how great things turned out. If there is anything I can do email me please, com . telebody @ mattr. Best wishes.

*Free advice to Tilly's employer, undoubtedly sifting this for incriminating evidence:
Tell Tilly it was all a huge mistake. Offer him a raise or pay him two months' salary as an apology. Offer to renegotiate his work contract so that he can continue to be productive for you while doing his hobby, which is contributing to the open source community, and if you like something he has, buy a license if necessary! Better yet, use it and his friends' work for free! Publicize your name and how you are a forward-looking company, and you will do wonders for your future bottom line with the support that will come in. Fail to do so and you can always wonder when the other shoe will drop. Perhaps a new product will one day inexplicably come up against a passionate, superior, free open source competitor. Ever have an elephant by the tail before? Tilly is one of the highest ranking members of a global community that can eat your nuggets for breakfast. Think. P.S. The legal minds on Slashdot (surf at level 4) think you are out on a limb. Cut your losses while you are ahead. Sincerely, Matt Rosin.

In reply to Re: Professional Employees and Works for Hire by mattr
in thread Professional Employees and Works for Hire by tilly

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others meditating upon the Monastery: (7)
    As of 2020-02-20 17:41 GMT
    Find Nodes?
      Voting Booth?
      What numbers are you going to focus on primarily in 2020?

      Results (91 votes). Check out past polls.