Personal code repository for further consulting

Question

I've started as a developer a few months ago (c#/vb.net) and I am keeping a folder in my "pendrive" (not really a pendrive) of all the sourcecodes that i modify, with all problems i solve, and solutions i create (profissionally). That may somehow violate the policy of where i work, because everything i do is their legal and intellectual property. I save it because i may use it while still in this company (or not), and so i can consult it to reuse it or just to read it and remember in case you have a similar issue to solve.

Is that common ? is it wrong (confirming) ? do you do something similar ?

----[UPDATE]---------

I gave up keeping codes I write. Thanks for the answers!

Answer 1

I would say its wrong. If you were to work on something that revolutionises the way that your system or system that every one uses and makes your company lots of money will then be spread around harming them as a company. If you did use a pendrive and you lost it or it was stolen so are your companies secrets.

If your company does find out that you are doing this its normally an offence so great that they can get rid of you straight away and then sue you.

Answer 2

If you're only taking utility/helper code you wrote yourself, while illegal, you're probably not a huge risk to your employers. I say this, because if you wrote it, then presumably you could recreate it for a different project without much effort. If you're taking proprietary algorithms or frameworks that you didn't write, (even in some cases those you actually did write), then I would have a problem with it as your employer, and if I ever found out that you used them in another project you can bet I would file a suit.

I honestly can't remember the last time I had to solve the exact same problem with code twice, so in my experience, I would say that it's just not worth the risk (or temptation) to keep proprietary code around.

Answer 3

I think this strongly depends on the nature of the code and the nature of your client's business.

If the code you're storing is strongly related to your client's business, then I wouldn't do it. e.g. I work for financial houses, so I wouldn't store stuff related to efficient pricing algorithms, say.

If the code is not related and generic, then I tend not to have a problem with this. e.g. I've stored SQL snippets for efficiently producing paged results, Java for setting up complex JMX monitoring setups, and other infrastructure/generic code snippets. I ensure that they are anonymous (packages changed to hide client's domain names etc.). Not because I'm concerned I may be found out, but simply to protect my client's confidentiality.

You may say that a lot of code related to your client's work is common knowledge (e.g. in the above, pricing algorithms). I might agree - however I don't want the hassle of even having to argue this. Hence my (possibly arbitrary split).

And (obviously) strip out server names / logons / passwords etc.!

Answer 4

As you have said in your question,

"That may somehow violate the policy of where i work, because everything i do is their legal and intellectual property".

On the other side, it is common to some extent but it is wrong any way.

You said you are new to programming, it feels like the code you write once, is probably the precious of all things, but it's not. There are millions of implemented modules (open source ) and samples out their to help you. If you need help use that or stack overflow, but you can't keep that code.

What will you think of someone working for you does the same ????