Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Source Code and Employers

Source Code and Employers

Scheduled Pinned Locked Moved The Lounge
questioncareer
9 Posts 8 Posters 1 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • V Offline
    V Offline
    valikac
    wrote on last edited by
    #1

    Hi, I often see job adds that mention that the programmers should bring along source code of past projects. In sum, what if employers were to make copies of the source code and then turn around and not hire you? Kuphryn

    N N P U R 7 Replies Last reply
    0
    • V valikac

      Hi, I often see job adds that mention that the programmers should bring along source code of past projects. In sum, what if employers were to make copies of the source code and then turn around and not hire you? Kuphryn

      N Offline
      N Offline
      Navin
      wrote on last edited by
      #2

      Oh, just post an article on CP, and use that. That way if they want the copies but don't want to hire, they can just come here, and you save yourself the hassle of an interview. :) No single raindrop believes that it is responsible for the flood.

      1 Reply Last reply
      0
      • V valikac

        Hi, I often see job adds that mention that the programmers should bring along source code of past projects. In sum, what if employers were to make copies of the source code and then turn around and not hire you? Kuphryn

        N Offline
        N Offline
        Not Active
        wrote on last edited by
        #3

        It goes without saying that if they would steal the code in such a manner you probably wouldn't want to work there anyway. I certainly wouldn't hand them over an entire application, just snippets.

        1 Reply Last reply
        0
        • V valikac

          Hi, I often see job adds that mention that the programmers should bring along source code of past projects. In sum, what if employers were to make copies of the source code and then turn around and not hire you? Kuphryn

          P Offline
          P Offline
          ProffK
          wrote on last edited by
          #4

          That must be subject to you owning the intellectual property rights to the source code, unless they mean source code from your own projects only. Hallelucination - when you think you see God

          1 Reply Last reply
          0
          • V valikac

            Hi, I often see job adds that mention that the programmers should bring along source code of past projects. In sum, what if employers were to make copies of the source code and then turn around and not hire you? Kuphryn

            U Offline
            U Offline
            unitrunker
            wrote on last edited by
            #5

            Unless your past projects were academic, I suggest politely explaining to the interviewing company that your past projects were all works for hire owned exclusively by the past employer or contract holder. Disclosing code not owned by you would be unethical and possibly illegal. Further, if they decide to hire you, they would also benefit from your zeal in guarding their source code and related proprietary information from unauthorized disclosure or plagiarism. If you do offer any code snippets, make sure they are (1) your own original work, (2) not used in any for-hire project, and (3) contain a clear copyright notice in the source code text. (Yes, a CP article would be an excellent way to do this). ;^) -rick

            T 1 Reply Last reply
            0
            • U unitrunker

              Unless your past projects were academic, I suggest politely explaining to the interviewing company that your past projects were all works for hire owned exclusively by the past employer or contract holder. Disclosing code not owned by you would be unethical and possibly illegal. Further, if they decide to hire you, they would also benefit from your zeal in guarding their source code and related proprietary information from unauthorized disclosure or plagiarism. If you do offer any code snippets, make sure they are (1) your own original work, (2) not used in any for-hire project, and (3) contain a clear copyright notice in the source code text. (Yes, a CP article would be an excellent way to do this). ;^) -rick

              T Offline
              T Offline
              Ted Ferenc
              wrote on last edited by
              #6

              rfmobile wrote: owned exclusively by the past employer I was about to write the same, I am 100% in agreement with you. After all if you are prepared to "steal" source code from your current employer what else would you do?


              "The greatest mistake you can make in life is to be continually fearing you will make one." - Elbert Hubbard

              1 Reply Last reply
              0
              • V valikac

                Hi, I often see job adds that mention that the programmers should bring along source code of past projects. In sum, what if employers were to make copies of the source code and then turn around and not hire you? Kuphryn

                R Offline
                R Offline
                Rob Manderson
                wrote on last edited by
                #7

                I applied for a job once (got it btw) where they wanted to see some source code. I chose to show them the source code for a games chat client I wrote (for free download). I wasn't making money from it but I was very concerned that showing them the code would not compromise server security. So I insisted they sign a non-disclosure agreement. They understood my reasons and respected the NDA :) Rob Manderson http://www.mindprobes.net "I killed him dead cuz he was stepping on my turf, cutting me out of my bling the same way my ho cuts cookies, officer" "Alright then, move along" - Ian Darling, The Lounge, Oct 10 2003

                1 Reply Last reply
                0
                • V valikac

                  Hi, I often see job adds that mention that the programmers should bring along source code of past projects. In sum, what if employers were to make copies of the source code and then turn around and not hire you? Kuphryn

                  C Offline
                  C Offline
                  Christopher Duncan
                  wrote on last edited by
                  #8

                  kuphryn wrote: I often see job adds that mention that the programmers should bring along source code of past projects. I've been asked this from time to time in interviews, and my answer is always the same. Source code from previous clients or employers is their proprietary information, and I honor that just the same as I would the code I write for them should they hire me. There's been a couple of times where the response was that they had no interest in the code at all - they just wanted to see what kind of person I was. That's something to keep in mind, no matter what question they ask you. The world is full of good coders. Consequently, good ethics will very often set you apart from your competition and win the day. Christopher Duncan Today's Corporate Battle Tactic Unite the Tribes: Ending Turf Wars for Career and Business Success The Career Programmer: Guerilla Tactics for an Imperfect World

                  1 Reply Last reply
                  0
                  • V valikac

                    Hi, I often see job adds that mention that the programmers should bring along source code of past projects. In sum, what if employers were to make copies of the source code and then turn around and not hire you? Kuphryn

                    V Offline
                    V Offline
                    valikac
                    wrote on last edited by
                    #9

                    There is no shortcut to software engineering. You either get the job done or you are out. Thanks for the thoughts. When asked for samples of past projects, I will bring the compiled program and a copy of some classes in the project. Otherwise, I will setup the interviewer's system to remotely log onto my home workstation and compile the project. Kuphryn

                    1 Reply Last reply
                    0
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                    • Login

                    • Don't have an account? Register

                    • Login or register to search.
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • World
                    • Users
                    • Groups