Skip to main content
27 events
when toggle format what by license comment
Mar 14, 2017 at 17:03 history edited BenYeomans CC BY-SA 3.0
added 871 characters in body
Mar 14, 2017 at 16:54 vote accept BenYeomans
Mar 14, 2017 at 13:51 comment added Steve Jessop Or possibly, they feel that an unmotivated developer in post will just contribute nothing, whereas an unmotivated sales guy doing nothing would damage relationships. The idea that you'd do intentional damage isn't the main risk -- it's the biggest possible harm, but it's incredibly unlikely that you'd want to wreck their system but choose to do that the day after you resign instead of the day before. If they fired you, they might feel differently about trusting you not to be malicious.
Mar 14, 2017 at 13:46 comment added Steve Jessop @Jocie: since sales guys are put on gardening leave and developers aren't, it's almost certainly about non-compete. For whatever reasons, they don't mind a developer with up-to-date knowledge of the code base starting work for a competitor the day after their last day at the company, but they're not happy with the idea of someone with up-to-date information about sales doing the same thing. Look on the bright side, maybe they just trust your professionalism more, to avoid making inappropriate use of inside information :-)
Mar 14, 2017 at 13:02 comment added RemcoGerlich @Jocie: you could do all those things before leaving too, so I don't see what's strange about it. Why would they stop trusting you after receiving your notice?
Mar 14, 2017 at 11:53 answer added Nivag Swerdna timeline score: 2
Mar 14, 2017 at 9:31 history edited BenYeomans CC BY-SA 3.0
added 323 characters in body
Mar 14, 2017 at 9:22 comment added Tim B @marcelm I've always worked out my notice anywhere I've left and I'd be surprised if anyone expected anything different. We just had a developer leave here who had to give 3 months(!) notice and not only did he work the full 3 months but he spent a fair amount of that time making sure everything was documented, handing things over, transfering knowledge, etc.
S Mar 14, 2017 at 8:30 history suggested xDaizu CC BY-SA 3.0
readibility
Mar 14, 2017 at 8:13 review Suggested edits
S Mar 14, 2017 at 8:30
Mar 13, 2017 at 20:28 comment added Oded @Brandin - and if the developer has the power to change production configuration and deploy to production? Or change one of the dependency DLLs to something malicious? Or... or... or... - There's a risk. Source controls doesn't mean there is zero risk. Assuming that code reviews happen or that every commit is reviewed is naive.
Mar 13, 2017 at 19:01 comment added Angew is no longer proud of SO @Jocie I confess I never understood why working during your notice period can be considered a risk. Where I live (Czech Rep.), a 3-month notice period is mandatory and can only be shortened by agreement of both parties. I don't think we have an abnormal number of leavers wreaking havoc.
Mar 13, 2017 at 18:32 comment added Brandin For developers you can just review the code they commit. What could they vandalize?
Mar 13, 2017 at 17:47 comment added NKCampbell Yeah...but when dealing with harassment type situation, all of those people are equally as liable for any potential suits and HR would deal with it directly with them and (should) ensure a stop is put to it one way or the other. The boat has sailed now but hopefully, they still circle back and bring it up with them all and discuss how a) entirely inappropriate the environment they created was and b) how extremely fortunate you didn't make a legal case out of it. Hopefully, the environment will at least be better for the next person. Good luck to you
Mar 13, 2017 at 16:21 comment added BenYeomans This does sound very much like what could happen I work in our business intelligence department so I deal a lot with their data... @NKCampbell I did think about it, HR even said in the exit interview I should have taken it up directly with them, but I felt I had lost the support of my line manager and the head of department and several people I spoke to about this also said she had the backing of a director who defends her if anyone critiques her in any way
Mar 13, 2017 at 16:18 history edited BenYeomans CC BY-SA 3.0
added 337 characters in body
Mar 13, 2017 at 16:15 comment added marcelm @Jocie "... and yet they made me work my four weeks notice ... I was shocked." - Where I live, it's fairly common to work out your notice period in full (assuming no conflict or other high-risk situation). Not everyone is that paranoid about quitter's vandalism.
Mar 13, 2017 at 15:54 comment added NKCampbell Given the description of the environment you provided - I'm more interested as to why this isn't a harassment conversation you are having with your lawyer and HR
Mar 13, 2017 at 15:13 comment added paparazzo Sounds like they are going to send you home and hopefully with pay. They may ask you to sign some agreement(s). Read the agreements. If there are some things you don't understand and are not comfortable with then consider checking with an attorney before signing.
Mar 13, 2017 at 15:11 comment added Vitani Not really an answer, so I'll post here, but I totally agree that this a garden leave. I gave my notice in at a software house where I had access to live servers and all of their code base and yet they made me work my four weeks notice ... I was shocked. I could have planted a time-bomb, wrote dodgy code in trunk, ruined their business but they were happy to risk keeping me working until my dying day. Oddly enough sales guys got garden leave, but developers did not. It was very strange. Don't sweat it, enjoy your paid leave.
Mar 13, 2017 at 15:05 answer added Chris H timeline score: 6
Mar 13, 2017 at 14:09 history tweeted twitter.com/StackWorkplace/status/841290177423257600
Mar 13, 2017 at 12:35 answer added Joe Strazzere timeline score: 22
Mar 13, 2017 at 12:02 history edited BenYeomans
edited tags
Mar 13, 2017 at 12:01 answer added Oded timeline score: 98
Mar 13, 2017 at 12:00 review First posts
Mar 13, 2017 at 13:16
Mar 13, 2017 at 11:56 history asked BenYeomans CC BY-SA 3.0