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
Search - "rant followup"
-
Summary of the summary: Boss is an asshole. Root gets angry; boss leaves instead of picking a fight for once. This makes Root sad (and really angry).
Summary: Root has another interaction with her boss. The boss is an asshole. Root is a bitch. Root would have been so so so much more of a bitch if the boss actually fucking responded. Root is sad this didn't happen. Root might have gotten fired. That would have made Root happy. :<
-------------
Le wild blackout appears!
-- Conference call (the short-short version) --
Boss: *freaks out* Fix it! Why aren't you fixing it? You have to fix it.
Me: I'm already fixing it. 😕
Boss: You have to fix it! This is important!
Me: Then let's get off this call so I can focus on fixing it!
Boss: Okay but fix it! *begrudgingly hangs up*
-- Slack --
Me: (posting a running log of what I'm doing) This is what i discovered. this is the cause. these are the possible fixes. I picked this one because it's quick and has few consequences, though it may break ____ so it'll need followup fixes. I'll do those tomorrow. Blackout resolved!
Boss: (apparently doesn't even noticed I fixed his shitty service)
-- Next day --
Boss: I want you to work on [stupid shit] instead.
Me: But what about the followup fixes?
Boss: Top priority! because customer service!
Me: ... fine.
-- Next week (verbatim because wtf) --
Boss: Did we test that [resolution] on ______? No one thought to test this. It didnt cross anyones mind at all? Either you guys can make good decisions and document concerns or I have to be part of every decision [...]. But this is basic. SHould have been a team heads up and said if we are switching this what can it break and can we test it. [sic]
Me: Did you want me to resolve the blackout quickly and allow people to actually use our service, or spend two days checking everything that might possibly have gone wrong? I weighed the possibilities and picked the solution with the quickest implementation with the fewest consequences. You're welcome.
Me: (Quotes boss's "SHould have been a team heads up" and links my "this is what could go wrong" heads-up in Slack)
Boss: (pretends not to even notice)
Boss: (talks about customer service related crap)
What a fucking loser.
I'm so angry he didn't respond and start in on me over it. I wanted to tear him to shreds in front of everyone.
Related:
He tried adding another huge project to my plate earlier today, and I started flipping out on him for all these shitty sales features he keeps dumping on me in place of real work that i still get blamed for not finishing. The contractor stepped in before it got too heated, though, which is probably best because my reaction was pretty unprovoked. The above rant, though? Asshole doesn't read, just blames and yells when he's angry.
I really hate him.20 -
PO: "I'll email you the details."
Me: Sure, I'll start with what I have right now.
I start coding, 7 hours later I got something working, not sure if it's what he wants.
Still no email.
I might have a followup rant tomorrow when he tells me it's not what he wanted at all.3 -
This is a followup to my earlier RealTek networking rant.
After reviewing and researching all of the wlan adapter suggestions on that rant, as well as a few more, I settled on an Alfa AWUS036ACH usb3 wireless-ac adapter. Every Alfa I've ever owned has been amazing, so I happily bought it.
It arrived today, and I excitedly threw my existing RealTek garbage across the room, hooked up my fancy new toy, and... nothing.
Fearing it was doa, I ran `lsusb` to see if it was even showing up... and it was! but identifying itself as a RealTek device...?
All of my research showed it uses the Atheros9k chipset. It's advertised and praised as using the "famous Atheros AR9271 chipset" and the Ath9k drivers. Except this particular unit appears to use the RTL8821AU chipset, therefore requiring RealTek drivers. askfja;sldf.
I unhappily fetched the garbage from the dirty laundry where it landed, installed it, and began my research anew.
I found, among all of the wonderful promises of Ath9k bliss, a thread on the Kali forums corroborating the RealTek driver nonsense, and it explained how to get the RTL8821 drivers working with it. which is pretty much the very last thing I want to do.
If you've read any of my networking rants, well, they've all been about how totally awful RealTek linux drivers are, and that's pretty much common knowledge anyway. So I'm like extremely pissed off.
ARGH WHY IS NETWORKING WITH LINUX ALWAYS SO FREAKING DIFFICULT? haslkfjasgdskg6 -
Followup to my job-hunt rant from December
https://devrant.com/rants/6137401/...
In the time since then, I got 5 offers from various companies.
I accepted the highest paying one.
Today is my first day as a (mostly linux) system engineer for a renowned e-learning company.1 -
Kind of a followup on my earlier rant, it seems like my "teacher" doesn't even really know C++. He replied to me that "the code doesn't work", which is probably because the code needs the compiler flag for c++11 (I barely even know what I'm talking about here), which he would've known *if he looked at the error message*?!
Have I mentioned enough yet that I STARTED LEARNING C++ LITERALLY ABOUT 2.5 WEEKS AGO?!?! OTL5