Like 50 seconds after getting inside the company, the engineer was approached by a douchebag in a business suite. There once was a bright young engineer who was hired by a company to design their new light ship. This is why we can't trust you to get things out. Maybe you should have prioritized it more, or written up better notes. You know it's bringing down production, and it's kind of urgent. Hey Root: Why did you take so long on this ticket? It has sat for so long now that someone else filed a ticket for it, with investigation findings. Nevermind that you provided snippets to remedy exactly scenario in the ticket description you wrote three months ago. we just don't know if it's good enough.Īlso, we goofed up when deploying and the testing database is gone, so now we can't test it since there are no records. don't know how to get the query it's running out of the code. Even though the changes are pretty minimal, you've said it's 8x faster, and provided benchmark findings, we just. You know, the one that SysOps and Data and even execs have been demanding? The one you finished three months ago? Yep, the problem is still taking down production every week or so, but we just can't verify that your fix is good enough. We pulled your urgent fix ticket from the release. Yep, have complete access to the console and DB and query log. Yeah, I also don't know how to find the query it's running now. There was too much text filled with things like implementation details, query optimization findings, overall benchmarking results, the purpose of the new columns, and i just couldn't care enough to read any of that. What are these new columns? Where is the new query? What are you doing? And why? Oh, the ticket? Yeah, I didn't bother to read it. Could you explain exactly what you're doing in this ticket, because i can't understand it. Yeah, could you explain it while I don't bother to listen and talk over you? Thanks. Hey, Root? How do you test your slow query ticket, again? I didn't bother reading the giant green "Testing notes:" box on the ticket. After i got paid, set an auto-reply of LOL to thier emails and chilled for a week before restoring the domain back to normal. i asked for an extra 10% penalty apart from the remaining payment. Got an apology mail from them 2 hours later begging me to restore the website. I created a github page with the text " This website has been siezed by the government as the owner is found accused in fraud" and redirected the domain to it. I sent them a final mail with warning ending with a middle finger emoji. Thinking that they have been successful, they even published ads about thier NEW dashboard to their customers. I tried to login to the AWS account, only to find password had been changed.Įven my admin account on the app had been removed. Once i inform them that its done and ask for the remaining payment. But i could sense something fishy, so i did everything on their AWS account, except registered the domain from my account and set up everything. After a couple of more such exchanges, i agreed to setup their account before the payment. They rejected the request saying my work was not complete as i had not deployed on AWS yet. I complete the whole project and sent them the screenshots, asking for the remaining 40% payment. I got the next 40% also without any effort but they said they also needed me to deploy the code on their AWS account, and they were ready to pay extra for it, so i agreed. Once i receive the payment in full, only then i will hand over the code. Since i had to deal with a lot of shitheads in the past, I told them my rules were simple, 20% advance, 40% on 50% completion and 40% after i complete and send them proof of completion. Why do shithead clients think they can walk away without paying us once we deliver the project !!!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |