Long story short I work at this shitty dysfunctional company stuck developing a huge feature basically alone where I'm comically overworked and understaffed. I'm basically a one person IT department, handling frontend, backend, db, infra fuckery etc. Not only that but on one side management constantly demands shit to be done, and on the other side, other company departments are constantly sabotaging me, with these petty little tyrants terrorizing me with their shitty rules. One of these rules is that we are in AWS and I'm not allowed to have a public IP addresses. For reasons I don't want to go into, one of our services HAS to have a public IP address, a fact I have tried to impress onto asshole management but with zero success so far.With the expectation of delivery bearing down my neck, I solved the issue by renting a server out of pocket and using that.Thing is I've described just how shitty a situation I am in, and unsurprisingly I've submitted my resignation (good fucking luck finding another loser willing to do the same shit as me). But the practical question is - on the last day I plan on powering down my external server, not out of spite, just because I have no interest in keeping it going.This will cause a huge fucking outage, and people will instantly suspect I'm committing some kind of revenge plot against the company.How fucked am I? How can I avoid liability?
>>103221004Shut it down now before you even leave
>>103221004You got paid for developing and deploying in production an application that does not comply with imposed restrictions and intentionally obscured that.If you were a contractor that would qualify as fraud.
>>103221004>I solved the issue by renting a server out of pocket and using that.This is absolutely a mistake. It's called "shadow IT" and can get you in a pile of legal trouble if something goes wrong. Your only solution is to put the people who insist that thing has to be done in the same room as the people who are preventing you from doing the thing and getting them to fight each other. Nothing you do will help this situation. There is no world where you should be working yourself to death for assholes.Also, document everything. Every email or text where the group says "no, you can't do the thing." Every email or text where the other group says "you absolutely must do the thing." When one group or the other gets upset, you send them all the email from the other group. Do *not* accept voice communication.
>>103221004What exactly is on the external sever? Company data?
You made a mistake as soon as you decided to use personal accounts and money to set up something for that job.Your best bet is to pay the bills and keep it running like a year or more, and then when you take that shit down they'll be less likely to trace it back to you - until they hire somebody to do that job.OP you'd probably be better off moving away lmao
They absolutely will have thousands of applicants when they list your position. lol. Just shut it the fuck down now. You're fucked, dumbass
>>103221459If OP is a fresh graduate then he is just inexperienced to know what to do
you've done just about the stupidest moves you could. bite the bullet and try to explain and clear the situation with all parties or expect to get fucked sooner or later
>>103224459>bite the bullet and try to explain and clear the situation with all parties or expect to get fucked sooner or laterI was gonna advice something similar but I wasnt sure if they would just scapegoat OP completely for the potential legal liability>>103221004OP if you trust your workplace to be harh but fair then bite the bullet as the anon above mentioned. If you think they will just throw you under the bus then consult a legal expert around data privacy to see if there is a way to escape liability while undoing your wrongs
>>103221004you fucked yourself when you did it in the first place. warn them that the current deployment uses test infrastructure paid by you, and that you will shut it down pending your resignation. print this mail out. shut it down a few days before you leave.
>>103221004>I solved the issue by renting a server out of pocket and using that.This isn't solving the issue. This is retarded. You might have violated several data privacy laws depending on what data you handle. Make up a lie about it being some kind of proof of concept infrastructure that you would use to convince them to agree to it. You might be completely fucked.
>>103221004Get a new credit card and "forget" to update the subscription. Plausible deniability. Next time don't be a dumbass.
>>103221004You are just a code monkey. If you were an entire IT department, you would just do what needed to be done without asking "management" for their permission.
>>103224527>wasnt sure if they would just scapegoat OP completely for the potential legal liabilitysure, but the difference here is how malicious OPs actions will retrospectively seem. to be fair I have no idea how much it would matter in a court of law but I'd expect it to carry some weight.
SHUT IT DOWM GOYIMJokes aside, can't you just move everything locally and have the next idiot figure it out?
>>103224735The problem isnt that the payment, the original sin is company data was moved on to a 3rd party vendor without company knowledge. If OP stops paying it will get found out and he will risk legal liabilities due to it
>>103221004>With the expectation of delivery bearing down my neck, I solved the issue by renting a server out of pocket and using that....How did you talk yourself into this exactly? I think you fucked yourself pretty much no matter what.I'd go to someone higher up and explain the situation immediately, frame in it a way where you renting the server was an absolute necessity and not just you being retarded. Definitely you need this solved before you leave, otherwise it doesn't really matter what your intentions are, you will basically be guilty of sabotage.
>>103221004Could you migrate it all to AWS directly rather than some data center noone knows about?If they get emails related to AWS cloud subscription the company will just pay it to keep things running
>>103221004>hi guys I'm a mechanic, I'm overworked so one time instead of working on a car at the company facilities I rented a lot and started doing work there, is it a problem if I just quit and leave the car I was working on there and don't tell anyone?
>>103225080not a perfect analogy, but it sends the right message
I don't know how the solution isn't fucking obvious, literally just transfer ownership of the server to the company, you're going to look like a retard no matter what but what's the worst that's going to happen? They're going to fire you? Think you're a retard?
Say "QA is over guys, we need more servers asap"
>>103225045Exactly on point, this is why I (>>103224549) would recommend saying it's just "test infrastructure" that got left around. Plausible deniability
>>103225138He needs to migrate it onto company infrastructure first
>>103225137The money guys would ask proof before approving more costs
>>103225151No he doesn't, if he actually stopped being a massive confrontation adverse faggot he'd just walk up to his supervisor and say:"I'm a fucking retard but to get my job done I, out of pocket, got my own server, before I leave the company we need to either migrate this to your own server or you need to take over the server already deployed". You put the ball in their court and outside of coming off as a fucking retard (which you are) you basically absolve yourself of wrongful intent.
>>103225171Yeah that does seem the best option even if there some chance of OP getting fucked over from potential legal liabilities
>>103225186It's very unlikely anything his does has legal liability because otherwise the company itself would be fucked for having zero oversight over his code and what he's been deploying.
>>103221004>renting a server out of pocket and using that.
I think OP learned his lesson not to do this again, next time just get fired when they ask for ridiculous shit that cannot be done instead of bending over backwards personally for it.If they're spiteful you might consider getting a lawyer so you can gracefully handle it. Start documenting everything, hopefully your demands and explanations that the server is necessary are written down. But yes they're free to pull the "you put our data on unsecured third parties we want every cent we ever paid you" even if its bs.
>>103225420Going personally out of the pocket should be the red flag that what you're being asked to do is insane. If you can't fit your job in your 9-5 and with company resources, what you're doing shouldn't be done.
>>103221004You fucktard.
