Details
-
SkillsJava, C
Joined devRant on 3/19/2018
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
-
So my computer froze, just after I clicked on Toto Africa song on YouTube, and it was still playing it.
It’s the chilliest freeze that I’ve ever had1 -
!rant
Went to see my brother today. Before I could say hi, I saw the following:
- Desktop, Windows playing video
- Thinkpad, Linux mint, Arduino IDE
- Arduino board with some sensors
- Coffee
- Complaining about light theme
I've only thought him a bit of C# and SQL. They grow up so fast :')
(Before today, I only knew he was gonna learn Python)3 -
TL;DR: I “hacked” my thermostat.
I’m stuck with an annoying roommate in college dorms who apparently always keeps the FUCKING thermostat at 80F. LIKE WHAT THE ACTUAL FUCK IS WRONG WITH HIM. Every time I change it to like 73F, he changes it back to 80F Heat.
Getting tired of his shit for over a semester, I decided to do something about it. I looked up the thermostat made by HoneyWell and downloaded the product manual of it. Turns out, they have a system override ability to remove the heating mode and change the maximum and minimum values of temperature.
BOOM! I removed the heating mode and changed the minimum value to 70 and max to 74.
It’s 2AM here and I can finally go to sleep without sweating my balls off. I’ll keep you guys updated on his reaction hahahaha.28 -
Is it normal for every stupid, arrogant, selfish person to talk all kinds of bad stuff about my app and attack me personally on the play store? It's just a soundboard and it's free you pricks, be grateful for once and don't mind the god damn ads so much. I can't believe that shit.5
-
EDIT: devRant April Fools joke (2018)
-------------------------
Hey everyone! As some of you have already noticed, @trogus and I made a decision (based on the suggestion of some members of the community) to start transitioning all scores on the app to binary. We have started by making all user scores in our mobile apps and website (if you’re logged in) appear in binary. We think this makes the app more fun while remaining usable at the same time!
Please let us know what you think and happy binary-reading!90 -
so i just got fired 🔥 🔥 🔥 because i wanted a 200 fucking dollars raise after 1 year of work and sacrifices and feeling like shit.
200$ because i live in the 3rd fucking world, working with a stupid motherfucking boss (you know the fat old tone deaf cunt), he's american, and he brings projects from the US from clients paying thousands of dollars, and he pays us 300$, and by the fucking way he used to pay us 100$ (we are 3 developers, a dick who does nothing but report our behavior, and a shit who does shit. we are a development company and we are the only developers and we got fired because he thought we didn't deserve the raise and that he sees no reason in giving us more money because we're already wasting the company's money and time).
So now the only people left there are the dick, the shit and the fatass boss who's in the states rn.
the funny thing is after we left by an hour or so we got calls from many other companies that we refused to work with because of our loyal-fucking-ty.
the motherfucker thinks we're conspiring against him, that we don't trust him, well of fucking course we don't, he lies about having a company in the US, well it's there but it's suspended (we looked it up), he says he's a microsoft, intel, adobe, dell, lenovo partner, and he's not.
well fuck i'm kind of happy that i left, i'm sitting with my friends in a cafe right now thinking about finishing our personal projects.
forgot something: the projects we were working on are unfinished, and there's not a single fucker to finish them, so he's ball deep in shit. hope this rant is relatable40 -
"You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!"
So, as the author of the code in question, I join the bridge... And what happens next, I will simply never forget.
First, a little backstory... Another team within our company needed some vendor client software installed and maintained across the enterprise. Multiple OSes (Linux, AIX, Solaris, HPUX, etc.), so packaging and consistent update methods were a a challenge. I wrote an entire set of utilities to install, update and generally maintain the software; intending all the time that this other team would eventually own the process and code. With this in mind, I wrote extensive documentation, and conducted a formal turnover / training season with the other team.
So, fast forward to when the other team now owns my code, has been trained on how to use it, including (perhaps most importantly) how to send out updates when the vendor released upgrades to the agent software.
Now, this other team had the responsibility of releasing their first update since I gave them the process. Very simple upgrade process, already fully automated. What could have gone so horribly wrong? Did something the vendor supplied break their client?
I asked for the log files from the upgrade process. They sent them, and they looked... wrong. Very, very wrong.
Did you run the code I gave you to do this update?
"Yes, your code is broken - fix it! Production is down! Rabble, rabble, rabble!"
So, I go into our code management tool and review the _actual_ script they ran. Sure enough, it is my code... But something is very wrong.
More than 2/3rds of my code... has been commented out. The code is "there"... but has been commented out so it is not being executed. WT-actual-F?!
I question this on the bridge line. Silence. I insist someone explain what is going on. Is this a joke? Is this some kind of work version of candid camera?
Finally someone breaks the silence and explains.
And this, my friends, is the part I will never forget.
"We wanted to look through your code before we ran the update. When we looked at it, there was some stuff we didn't understand, so we commented that stuff out."
You... you didn't... understand... my some of the code... so you... you didn't ask me about it... you didn't try to actually figure out what it did... you... commented it OUT?!
"Right, we figured it was better to only run the parts we understood... But now we ran it and everything is broken and you need to fix your code."
I cannot repeat the things I said next, even here on devRant. Let's just say that call did not go well.
So, lesson learned? If you don't know what some code does? Just comment that shit out. Then blame the original author when it doesn't work.
You just cannot make this kind of stuff up.105