Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

how do you pass knowledge ?

Former Member

‎08-03-2006 3:50 AM

0 Kudos

Dear Gurus,

When rolling off, a developer may be asked to hand over knowledge of codes developed to the next person.

Is there no way to hide knowledge during such a process given that codes can be read by any developer?

I like to know how to handover without actually handing over knowlege as much as possible.

Pls share with me this skill.

Thanks,

t.d

3 REPLIES 3

Former Member

‎08-03-2006 3:53 AM

0 Kudos

I wonder why you don't want to do that!

Former Member

‎08-05-2006 3:41 PM

0 Kudos

Your employer has paid you for that knowledge. So if they ask you to pass it on to the next person, that is what you must do.

Former Member
In response to Former Member

‎08-05-2006 4:13 PM

0 Kudos

> Your employer has paid you for that knowledge. So if

> they ask you to pass it on to the next person, that

> is what you must do.

I agree totally. When we roll-off of a project and have "knowledge transfer", we go through a review process for each program. The developer meets with the client team lead and client developer. We do a code review and go over the functional and technical specification documents.

Some client contracts carry legal requirements. I have seen development objects listed as "type 1", "type 2", or "type 3". In some cases, the code is owned by the client and you cannot legally re-use it at any other site. Other cases declare the source code as "shared". You can re-use it at a new project. The third case may declare it is owned by the consulting firm or implementation partner. The client cannot share it with outside sources.