3 ms·

Had a dev use macro keystrokes to cheat it. worthless.

• shawn 8y ago
  Hahaha. What? That’s awesome. What did the macros do? I’ve always wanted to make a plausible code generator based on markov chains. It still seems like an effective way to trick people into thinking you’re working on some hard problem.
  • nihil75 8y ago
    No need for pseudo-code, random clicks/strokes will do (he used the arrow keys to move around code and switch open Atom tab).
• bredren 8y ago
  The thing is if you are working on a serious team there is no value to cheat. You need to generate quality code at a reasonable pace. Custom solutions don’t appear out of nowhere. So sorry to say but your dev setup was not good because you get 2 weeks to dispute this. I know because I have hired on here too and been scammed once. I raised all the red flags and ended up getting some money back even past the guarantee. Thing was that if I had reviewed the screenshots it was obvious it was bullshit.
  • nihil75 8y ago
    You get one week to dispute, and let me tell you - Upwork staff are not quick to accept your claims. By the time my dispute was manually reviewed the payment was already passed to the freelancer and could not be reclaimed. Only the most recent week's pay was refunded, even though the evidence suggested the developer was cheating for a long period of time. I didn't catch on because he was producing good code and just used the macro to "inflate" his hours by about 30%. I caught on by pure chance when he happened to tweak his background macro tool just as the hourly screenshot was taken.