Author Topic: proper response  (Read 3485 times)

0 Members and 1 Guest are viewing this topic.

estanima

  • Guest
proper response
« on: September 25, 2018, 10:56:11 AM »
What would you consider the proper response when a new employer asks you for 20 years of source code you've worked on? 

ChrisCarlson

  • Guest
Re: proper response
« Reply #1 on: September 25, 2018, 11:44:18 AM »
Source code is usually proprietary and confidential to a prior employer. I would inquire if a sample program would suffice as a method to show experience and capability.

estanima

  • Guest
Re: proper response
« Reply #2 on: September 25, 2018, 11:56:16 AM »
Source code is usually proprietary and confidential to a prior employer. I would inquire if a sample program would suffice as a method to show experience and capability.

Wish I could use my previous employer, but this was all stuff just I did on my own.

JohnK

  • Administrator
  • Seagull
  • Posts: 10638
Re: proper response
« Reply #3 on: September 25, 2018, 12:11:00 PM »
If this program was not open source and makes you money:
"A licence to use the program can be purchased for... However the source code is not for sale."

If this could make money for the company:
"For $x a separate/additional licence can be arranged and I would like x% of all profit from code in perpetuity."
TheSwamp.org (serving the CAD community since 2003)
Member location map - Add yourself

Donate to TheSwamp.org

dgorsman

  • Water Moccasin
  • Posts: 2437
Re: proper response
« Reply #4 on: September 25, 2018, 12:41:32 PM »
What would you consider the proper response when a new employer asks you for 20 years of source code you've worked on?

I'd provide them references for others who had used that work at other offices.  Unless you're being hired by an employer who only provides software, they won't really care (or possibly even understand) that much about the actual source code.  They're more interested in how well you implemented it, and how well it works with users.
If you are going to fly by the seat of your pants, expect friction burns.

try {GreatPower;}
   catch (notResponsible)
      {NextTime(PlanAhead);}
   finally
      {MasterBasics;}

estanima

  • Guest
Re: proper response
« Reply #5 on: September 25, 2018, 01:26:54 PM »
Essentially it's just another programmer in the company who wants it....who has been with the company for a long time, so the company is asking for it so he can check it out.

I don't know, seems like something no one should ask for.
« Last Edit: September 25, 2018, 08:14:46 PM by estanima »

MickD

  • King Gator
  • Posts: 3636
  • (x-in)->[process]->(y-out) ... simples!
Re: proper response
« Reply #6 on: September 25, 2018, 08:26:05 PM »
Essentially it's just another programmer in the company who wants it....who has been with the company for a long time, so the company is asking for it so he can check it out.

I don't know, seems like something no one should ask for.

Yep, it sounds like they're just looking for free code to save them time therefore money. Ask them to be specific as to why they want it, try to be amicable with them and explain your concerns and that 20 years worth of code is not something you're prepared to give up freely but (perhaps) you would be willing to use as reference/snippets as needed to help you and others.

If they're not looking for free code then a printed page or two of your code to display your style and ability should be enough.

Remember, you have been hired to 'work' on their code, not provide it :)
"Programming is really just the mundane aspect of expressing a solution to a problem."
- John Carmack

"Short cuts make long delays,' argued Pippin.”
- J.R.R. Tolkien

CADbloke

  • Bull Frog
  • Posts: 342
  • Crash Test Dummy
Re: proper response
« Reply #7 on: September 28, 2018, 06:10:42 AM »
I don't know, seems like something no one should ask for.
Exactly right.
If this program was not open source and makes you money:
"A licence to use the program can be purchased for... However the source code is not for sale."

If this could make money for the company:
"For $x a separate/additional licence can be arranged and I would like x% of all profit from code in perpetuity."
And those number should represent the value of handing over that 20 years of your work. Twenty. Years. If they want the source code, add at least two zeroes. I would add at least 3 zeroes.

If it's just some programmer looking for code to steal then that's not a particularly positive reflection on their character.


SEANT

  • Bull Frog
  • Posts: 345
Re: proper response
« Reply #8 on: September 28, 2018, 08:15:28 AM »
Essentially it's just another programmer in the company who wants it....who has been with the company for a long time, so the company is asking for it so he can check it out.

I don't know, seems like something no one should ask for.


Perhaps not. 

Do you now have access to all of their existing code?  That may have some bearing.
Sean Tessier
AutoCAD 2016 Mechanical

ChrisCarlson

  • Guest
Re: proper response
« Reply #9 on: September 28, 2018, 08:31:51 AM »
Essentially it's just another programmer in the company who wants it....who has been with the company for a long time, so the company is asking for it so he can check it out.

I don't know, seems like something no one should ask for.

Remember, everything has a price. If they really push the issue and you own the code you've written, sell them the code based on a sum of the "salary" you could or had made writing the code and multiply by 5.

estanima

  • Guest
Re: proper response
« Reply #10 on: October 05, 2018, 02:41:47 AM »
Thanks all.  Between this and some thought I came to this conclusion.

For them to ask for the code they are saying "your work is awesome and we want it"... but at the same time they are saying "we don't feel you are the person we want to continue to move forward with your own work, we like this other person better".  In my own opinion, a proper statement to me would have been "we are impressed with the work you've done and we want to stand by you to pursue it more".  I realized how incredibly dehumanizing it was for them to marginalize both my effort and me to a point they are asking to simply step aside from my own work and hand it to someone else.  Obviously they choose to not stand by me as I pursue my own efforts, so off to alternative work I think, they can figure it out by themselves, where I say good luck, 20 years was hard, and the amount of code I've written can fill at least a novel, if not two. They have a lot of work ahead of them.
« Last Edit: October 05, 2018, 02:45:00 AM by quadman »