Checkmate Flat Earthers

Our front-end team is pissed at me because they found a feature I pushed last month and claimed they didn't know it existed and how can they help clients if they don't know what's going on with the platform and - I pointed them to the Pivotal story of the feature that they were included in as well as the full changelog announcement I made to the entire team the day I pushed it.

Knowledge is power, especially when it's in writing with a timestamp.

Promising the boss a 95% model accuracy when the arXiv paper says it can only reach 86% is what I call self-checkmate

Are you familiar with chess? What classes/objects and methods/functions would you use to implement the game of chess? Who knows if checkmate is reached? What about timed games?

It always leads to an interesting discussion and you can easily throw out prodding questions if they get stuck. I've never had anybody give me the exact same answer, and it's been complimented post-interview a handful of times.

Procrastinates, wastes time not working; hates himself

Works on a regular schedule, putting in effort and feeling sleep deprived;
Hates himself even more.

Inner self hatred realises something.

Who said my self-loathing was bad for me???

My University's payment portal...
Check the captcha...
Checkmate scrapers!

I spent whole day for one client in order to implement ddos protected tunnel into his java based project. In exchange he was supposed to send me his source code of one of his projects. Fucker didnt send me anything. Good that while doing migrations for him I downloaded his compiled project backup, so all I had to do was decompile his jars which had no obfuscafion whatsoever, so I managed to salvage around 95 percent of his source code. Checkmate boi.

My ex-colleague contacted me recently to help build a solution that would checkmate the case of code theft that they are currently challenged with. I tried to suggest the developers either work remotely (using rdp or similar), or physically with a company provided system. He rejected both recommendations and insisted the potential culprit shouldn't be aware he is being monitored

He proposed the following flow for what he intends I build: an obfuscated program scattered across the code base, possibly assembling at intervals or as a reaction to project build. Then signaling their server with details of the machine it's running on

The project to be rigged with the spyware is written in spring boot and I can't turn this down even if I don't think it's worth it cuz no work has been forthcoming and I'm nearly out of cash

So the question is, is the flow described above a feasible one? Can you suggest a smarter way to detect when the code is transferred to the system of an unaccredited engineer? Can you suggest any tips on how to go about this?