Plot twist - he works for a porn website.
Layoffs have never been easier. Genius.
As if they ever needed a reason.
In some countries they do, but yeah, not in the US.
Bro was just doing bug bounty lol
That would acutally makes sense. Pornhub has some of the most skilled system and software engineers out there and they are doing really advanced network communication stuff. There are definitly things to learn from their tech stack.
Classic developer move. Always debugging!
I used to work on a browser. My whole team got flagged for watching porns. Haha. The reason we gave was that these were the highest hit links.
Number 7 a developer watches prawn and gets naykid
Understandable
'Just checking API calls'. The new 'I was just checking for viruses'
He was just calling his own api.
Source?
I’ve worked at firewall companies where we had to test the products ability to block porn and other categories. What surprised me is not getting a call from IT after testing it.
Sometimes you need to look past the problem to see things more clearly. I’m sure he was just letting his subconscious take a whack at the issue.
My cum was piling.
What?
I said my code was compiling. What did you hear?
that's why you just remote into your home computer like I do I don't do that nope I'm working every hour I'm in the office sure am boss no fun going on here nope none at all what so ever nosiree jim bob you betcha.
I worked at a co-work space with a firm that optimized PPC ads. One of their clients was Cam4. It was a running joke he was always looking at porn.
The grind never stops 💪
Exploratory testing
In my last company, on a company-wide teams call, the company's lawyer shared his screen to everyone, CEO, CFO, HR, EVERYONE, and it was on pornhub.
I still do not understand how your brain would allow that to be something that happens.
Worked for a semi-major mobile provider, and we received a message about a pornography site not working.
Me: "Well, it's going to be hard to validate the fix if we can't visit the site."
Coworker: "You don't understand... WE HAVE TO!!"
Maybe he was just debugging a site traffic issue in real-time!
Just PUTting in requests, GETting caught with the payload... wasn’t expecting a 403 from HR.
Gonna take some time to PATCH things up POST-termination.
I mean what were his other OPTIONS?
More like he was 401 in first place