Forum Replies Created
-
Posts
-
UMost assumptions are correct, except:
>If the task is incomplete
If you read the question carefully, you’ll see that the task is *complete*. The tech part was also mostly complete, and while some bits and pieces had to be indeed solved in-house. That was the crux of all issues: that dude’s attention was all over the place and he barely knew what he was doing, and didn’t realize that it was over. I take it, when he understood that, he resorted to sabotage. He explicitly told me that his payment issues were with *other* projects, which is the next level of insane: it’s like shooting a bystander who happened to say “hello” to a guy you don’t like.
UIn this particular CMS it’s not supported. As for the access we gave them, well, they were the developers, and all the drama was unfolding behind our backs.But it wasn’t some sort of a super hack, just a silly oversight in a chaotic situation. As a half-full glass though, the guy helped us find security holes, which is always a good thing before going live, and make sure that our backup procedures run properly. So looks like everything is well now on our side.
Still, thank you for the advice.
UIt’s all blocked now, but thank you for the advice.Looks like it’s not relevant anymore. But I wonder if such a situation arises again, is there a legal solution for this kind of stuff?
UThank you for your advice.The local designers are not in violation of my contract (the contract doesn’t explicitly say that everything is to be handled in house), and they are very small not to mention suffering themselves. Most importantly, I doubt it’ll solve the main issue.
I am more interested how to keep the crazy idiot away. Any practical/cost-effective way to do that in India?
