• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Workplace ethics question

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
You can use the apps as a personal reference and testiment to your work ability. I know people who take copies of policies/procedures/apps from job to job and used some of them for guidelines on how to implement a new policy/procedure/etc etc at their new work place. I'd keep it, but it's up to you though.
 
Hmm... oddly, I do 90% of the program writing in my head - determine what routines I'll need, etc. That's usually while I'm watching tv, taking a shower, etc. Then, when I sit in front of a computer, I'm just typing it. In other words - I write it on my own time, I enter it into a computer on their time... it's mine 🙂
 
Keep it. It's not like you couldn't recreate it or make an approximation--you're the author! And your old boss is a shmuck, and you should have been compensated instead of tooled.
 
I would keep it. I wouldn't even hesitate to write something similar if I were to work for another company. Just make sure you keep it on the down low.
 
OK, it was a paid internship, so what?

As it stands, you probably signed something that hands over what you do to your company.

As for asking for money, that is such a dumb idea. He is on a coop/internship, not a consulting job. It's a privilege to do one as the reason he is there is for the learning experience. Asking for money would just burn bridges between him and a possible future employer...

You don't have to delete it, but don't tell them you kept it. On your next coop, don't even think of doing code that resembles what you did in the other job.
 
FYI, people have gone to jail for taking code from their old employer to the next. Avant! Cadence case comes to mind. So if you keep it, don't even think about cutting and pasting, or using any fragments of the code. Also, since you don't have the same security measures that your employer may have had, if someone ever hacks your computer and gets their hands on your code and leaks it, you will be in trouble if your old employer finds out.
 
Originally posted by: SuperTool
FYI, people have gone to jail for taking code from their old employer to the next. Avant! Cadence case comes to mind. So if you keep it, don't even think about cutting and pasting, or using any fragments of the code. Also, since you don't have the same security measures that your employer may have had, if someone ever hacks your computer and gets their hands on your code and leaks it, you will be in trouble if your old employer finds out.


None of it is stuff that I could see cutting and pasting really.

All the app does is read in specific ethernet packets, parse the nfo, and create a series of html pages.
 
Originally posted by: Gibson486
OK, it was a paid internship, so what?

As it stands, you probably signed something that hands over what you do to your company.

As for asking for money, that is such a dumb idea. He is on a coop/internship, not a consulting job. It's a privilege to do one as the reason he is there is for the learning experience. Asking for money would just burn bridges between him and a possible future employer...

You don't have to delete it, but don't tell them you kept it. On your next coop, don't even think of doing code that resembles what you did in the other job.

that's retarded. yes, he shouldn't use any kind of proprietary stuff in other jobs. but lets say he figured out a way of doing something. lets say solving some kind of general problem that would be encountered in other jobs.

based on what you're saying, if he uses the same methodology and writes a solution to the same kind of problem using code that most likely looks very similar to the code he wrote before, its "wrong." stuff like that is by no means wrong at all.
 
Back
Top