Ranter
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
Comments
-
Did they accept those quotations? If so and it was all signed off, then you have a good legal basis to recover the funds.
Don't start screwing around, otherwise that will kill any legal basis you have, and possibly allow them to come with a lawsuit after *you*. -
Client agrees to pay for services rendered.
You render services.
Client doesn't pay for rendering of aforementioned services.
You take your services back because they belong to you. -
As much as it would (temporarily) feel good to screw them up, it's better to be smart about it.
Definitely do NOT destroy anything (not even if you have a backup).
You can try creating disruptions in their services (scheduled downtime for minutes/hours/days) but they can then come after you for damages (loss of revenue) that could surpass what they owe you and after both cases are resolved you'll end up behind financially and emotionally.
What I've seen working is that devs (like yourself) owned entire websites kept everything functional but added a permanent banner (like Wiki begging for funding) shaming them for not paying their vendors. They will probably call you as soon as their users see it. But be careful what you write as if not 100% they can file for defamation.
You can also engage layers or your local Tax department, no body likes being audited. -
@BobbyTables well the code is on GitHub , so not sure if taking back services would work .
They would simply revert .
Deleting branches is not something I can do since they have backups weekly of all branches. -
@AlmondSauce the mails we exchange have work related information .
Regarding payments and terms , they did it over whatsapp calls (no recording) and over normal calls (recording available).
So it is not as bad as it seems legally.
There is a clear understanding from the communication evidence that I have done work and they do owe me money . -
@LordPeeve honestly , I feel to bury them in AWS costs is the most straightforward solution I can think of.
Basically copy their access keys and spin up heavy expensive machines spin up and run crypto mining all over them. -
@ironhide0396 Mate, there are many ways to incur cost for them if you have control over their infrastructure. However, whatever you do to incur unsolicited cost will certainly be seen as malicious and they can later legally come after you to reimburse them. So I'd steer clear of such course of action.
This is not a "two thugs stealing from each other and nether can go to the cops" situation. -
@LordPeeve a friend of mine instilled this sense into me as well .
Thanks fellow dev.
Sometimes frustration peaks up because you put in real time and efforts and suddenly the client acts like jack ass -
@ironhide0396 All good mate.
We cannot avoid temptation but we can control what we do with it 💪
In my case it took me over a year to get what I was owed. Hope you get your money soon mate 🤞
Related Rants
So I am pretty fair dev at Java and have been doing freelancing for sometime apart from normal full time job.
Got a client , a well funded one, who raised a decent chunk of money recently.
Got me do a couple of different areas right from refactoring and bumping their performance to all the way setting up AWS Services like RDS,Lambdas,Dynamo,SQS.
It was going good , money was coming in for the initial part.
Thinking that money is not the concern here , I accepted work at runtime and gave quotations about the additional work.
However now that all is done and deployed , the client simply refuses to pay me the money and has ghosted me horribly than my ex ever did.
I have access to their GitHub,AWS(I setup myself).
Need suggestions of whats the best way I can fuck them up if they decide to not pay even after a few more professional polite attempts I do .
sidenote : They had a pretty dumb db design and blindly had resorted to services in AWS and the pricing is still a major point of concern for them.
devrant
aws
asshole client
revenge
advice