Details
-
Skillsjs, java, html, css
Joined devRant on 10/21/2016
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I had a secondary Gmail account with a really nice short nickname (from the early invite/alpha days), forwarded to another of my mailboxes. It had a weak password, leaked as part of one of the many database leaks.
Eventually I noticed some dude in Brazil started using my Gmail, and he changed the password — but I still got a copy of everything he did through the forwarding rule. I caught him bragging to a friend on how he cracked hashes and stole and sold email accounts and user details in bulk.
He used my account as his main email account. Over the years I saw more and more personal details getting through. Eventually I received a mail with a plaintext password... which he also used for a PayPal account, coupled to a Mastercard.
I used a local website to send him a giant expensive bouquet of flowers with a box of chocolates, using his own PayPal and the default shipping address.
I included a card:
"Congratulations on acquiring my Gmail account, even if I'm 7 years late. Thanks for letting me be such an integral part of your life, for letting me know who you are, what you buy, how much you earn, who your family and friends are and where you live. I've surprised your mother with a cruise ticket as you mentioned on Facebook how sorry you were that you forgot her birthday and couldn't buy her a nice present. She seems like a lovely woman. I've also made a $1000 donation in your name to the EFF, to celebrate our distant friendship"31 -
There was a problem with a server we were staging on, and I was providing DevOps help remote.
As a joke I said, "haha if you run `sudo rm -rf / --no-preserve-root` everything will be fixed!"
They ran it. RIP server-kun 2016-2018 💨34 -
Had a customer on the phone who couldn't figure something out. Wanted to give him instructions so I asked him whether he used mac or windows (getting used to not including Linux in that question). His reply: uhm this has a weird name... do you know elementary os?
Me: you're a Linux user?!
Him: yes, I'm done with windows and mac.
Then i gave him the instructions. Nice twist of the day!12 -
Got call from extremely angry customer, our product is shit and doesn't work. At all. Important customer so I went to visit.
He had the perfect setup, our product to the left, our competitor's to the right.
He connected the Ethernet cable to their product, it worked. He plugged it out and connected to ours... Nothing. Shit.
I started to debug on the premises, took logs, everything. It seemed like our product didn't receive any data at all. What the fuck? Tried everything, debugged low level, still nothing. Sweating as hell.
After two hours I got a strange feeling. So I swapped place, our product to the right, competitor's to the left. Now OUR product worked, competitor's zilch.
THE FUCKING ETHERNET CABLE HAD A GLITCH. IF YOU BENT IT TO THE RIGHT IT WORKED, IF YOU BENT IT TO THE LEFT IT WAS BROKEN.
I had never seen a customer be this embarrassed in my life. He apologized to me, my boss, his boss, the Queen, everyone.
We got the contract.20 -
Sister called me on my way to work (she never calls me, we communicate through a family signal) to ask if I wanted to come over for dinner in the weekend because a new guy she knows will be there and also my parents.
Me: hmm idk I've got a lot to do in the weekend....
Sis: he saw my laptop by the way, he was highly impressed that its dual booted and asked how on earth I know about Linux! Then I told him about you and what you do and now he really wants to meet you!
Me: what time would I have to be there?
I hate how that stuff can make me change my mind just like this 😅25 -
STOP. LOOKING. AT. HALF. FINISHED. SPRINTS. FOR. STYLING. ERRORS.
For the love of god I know it's not right yet leave me aloooooone7 -
When you "fix" a bug not by actually fixing the bug but by disabling the user's ability to cause the bug.14
-
Girlfriend: What's your biggest fear?
Me: That machines take over the world.
Girlfriend: What?
Toaster: What?12 -
Another dev on my team just got a new machine. Before he came in today I made two separate USB installers and left him these notes.62
-
Oh, man, I just realized I haven't ranted one of my best stories on here!
So, here goes!
A few years back the company I work for was contacted by an older client regarding a new project.
The guy was now pitching to build the website for the Parliament of another country (not gonna name it, NDAs and stuff), and was planning on outsourcing the development, as he had no team and he was only aiming on taking care of the client service/project management side of the project.
Out of principle (and also to preserve our mental integrity), we have purposely avoided working with government bodies of any kind, in any country, but he was a friend of our CEO and pleaded until we singed on board.
Now, the project itself was way bigger than we expected, as the wanted more of an internal CRM, centralized document archive, event management, internal planning, multiple interfaced, role based access restricted monster of an administration interface, complete with regular user website, also packed with all kind of features, dashboards and so on.
Long story short, a lot bigger than what we were expecting based on the initial brief.
The development period was hell. New features were coming in on a weekly basis. Already implemented functionality was constantly being changed or redefined. No requests we ever made about clarifications and/or materials or information were ever answered on time.
They also somehow bullied the guy that brought us the project into also including the data migration from the old website into the new one we were building and we somehow ended up having to extract meaningful, formatted, sanitized content parsing static HTML files and connecting them to download-able files (almost every page in the old website had files available to download) we needed to also include in a sane way.
Now, don't think the files were simple URL paths we can trace to a folder/file path, oh no!!! The links were some form of hash combination that had to be exploded and tested against some king of database relationship tables that only had hashed indexes relating to other tables, that also only had hashed indexes relating to some other tables that kept a database of the website pages HTML file naming. So what we had to do is identify the files based on a combination of hashed indexes and re-hashed HTML file names that in the end would give us a filename for a real file that we had to then search for inside a list of over 20 folders not related to one another.
So we did this. Created a script that processed the hell out of over 10000 HTML files, database entries and files and re-indexed and re-named all this shit into a meaningful database of sane data and well organized files.
So, with this we were nearing the finish line for the project, which by now exceeded the estimated time by over to times.
We test everything, retest it all again for good measure, pack everything up for deployment, simulate on a staging environment, give the final client access to the staging version, get them to accept that all requirements are met, finish writing the documentation for the codebase, write detailed deployment procedure, include some automation and testing tools also for good measure, recommend production setup, hardware specs, software versions, server side optimization like caching, load balancing and all that we could think would ever be useful, all with more documentation and instructions.
As the project was built on PHP/MySQL (as requested), we recommended a Linux environment for production. Oh, I forgot to tell you that over the development period they kept asking us to also include steps for Windows procedures along with our regular documentation. Was a bit strange, but we added it in there just so we can finish and close the damn project.
So, we send them all the above and go get drunk as fuck in celebration of getting rid of them once and for all...
Next day: hung over, I get to the office, open my laptop and see on new email. I only had the one new mail, so I open it to see what it's about.
Lo and behold! The fuckers over in the other country that called themselves "IT guys", and were the ones making all the changes and additions to our requirements, were not capable enough to follow step by step instructions in order to deploy the project on their servers!!!
[Continues in the comments]26 -
Boss walked towards his office asking a coworker to do something.
Coworker replied that he'd like to but only the boss has the login codes or something like that.
Boss: ah right *walks to coworkers table* let me enter that stuff *starts typing*
Coworker: Maybe I'm running a keylogger 😏
Me: *exchanging funny eye contact with coworker* yeah maybe he is.... 😏
Boss: *looking back and forth at both our faces suspiciously*
Coworker: 😏😏😏
Me: 😏😏😏
Coworker: 😏😉
Me: 😏😆
Boss: 😐
*three of us laughing*
😆10 -
CEO: "What if we invest in our devs (i.e. trainings, certifications) and they leave?"
CTO: "What if we don't and they stay?"10 -
Hired a new backend Dev. He writes a script and sends it for testing...
Tester: "It's not working..."
Backend Dev: Goes to Mongo and deletes the tester's whole profile...
I cant control my laughter every time I remember this incident...He claimed it was a mistake, I don't think that it was a mistake...the tester had it coming...
"It's not working" that's all he says every time...I mean at least give me something to start with...!4 -
It's 2017 and you're not allowed to complain about syntax error bugs. Get a proper tool for the job.
We don't use rocks for hammers, and we don't use notepad for coding15