Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@katbreitin <3
-
Sounds to me like you will only have time to write half the code required before you leave.
After all, they can't sack you after you left for not finishing in time. :-)
Since coding is an art more than a science, no one can predict how long it will take to write X and Y.
After all, you don't want to rush it and not have time to iron out those bugs.
Perhaps you could focus on some key elements of the design, that you could finish in time, such as the front end only, so at least folk have something pretty to look at, with just a dummy backend to hold things together.
Remember to leave a note mentioning which bits still need coding by your replacement. -
@netikras
If they weren't to blame the leaving employee for a production systems crash.
@martengooz !! -
@scor
"Hurr durr!
The key account developer was so bad, we had to let him go.
Here, instead, have our other super hero developer."
Now shut up and pay our bills. -
@scor I’m pretty sure that exactly the scam they are gonna pull.
-
@katbreitin best answer ever. It's your time that matters, not the customer's
-
@rov3rand0m I remember an ex of mine had that issue once, they asked someone in another department for price information on a product via a telephone call, and they gave an incorrect figure.
This error cost the company a lot since everyone and their dog wanted said product at the low price in the advert..
It took several days before anyone noticed it was advertised below cost price !
Now, if only that information has been sent in an email..
At that moment, said person went on holiday for 2 weeks !
But my ex got the blame, because they believed the other person more. -
@rov3rand0m
Reminds me of a place I left, and a couple of weeks later someone I knew from there emailed me to ask if I'd sabotaged the place !
No, I said, the reason why everything has ground to a halt practically is because I'm not there to fix everything !
I left the place in tip top condition with everything functional.
Kinda like when I left an ex and made sure the I fixed the washing machine on the same day.
I quit and my last day is next week.
Apparently management has decided that I should spend my last day implementing a new feature for a customer where I have been the only developer, and release it to production (without first implementing it in test) the same day. A feature that potentially could cripple a whole workflow if done wrong.
Of course I advised not to release untested code to production on a friday, just before the only person that knows how it works leaves the company. But no, “the customer reaaaaaally wants it before summer, so just be careful not to write any bugs”.
I’m not saying that I’m intentionally gonna write bad code - but if I do, I’m not gonna pick up the phone when it calls.
rant