Public Voice Network
- FACE EATER 11
- Music over 5.1 System
- Video Cameras Under $2000 77
- the gif animation thread 1283112831
- ATTN: Greedy Republicans 2323
- What is THEIR work? 44
- Pic of the Day 6330063300
- News of the day... 136136
- Chick of the Day 1537915379
- Letterpress process video 22
- New York 44
- Show your latest Pics 32943294
- XBMC 33
- what happened? 2222
- F1 2012 1919
- Vid of the Day 1203312033
- paper trail 88
- Facebook IPO 156156
- Diablo III 8383
- Coda 2 3434
- Euro Crisis 66
- In Dallas for a month 1212
- shopped? 66
- Oh Amazon. 22
Firing a programmer- Help 4343 Responses
Last post: 2 years, 2 months ago | Thread started: Mar 5, 10, 1:52 p.m.
Out of context: Response #15 [Mar 5, 10, 1:52 p.m.]
- ryoshu
Shut down any accounts that were assigned to him; change passwords on any shared accounts; shut down his company email; ask him to delete any company or client code he may have. If you're worried he might have done something in the code (back doors), a code review may be in order, but only really skeevy developers do that sort of thing.
Another thing that seems small, but actually goes a long way is to wish him good luck and say something along the lines of, "sorry it didn't work out." You don't want him to take the decision personally. Good will goes a long way in making sure people don't try to screw you later.


- View thread



