Navy story time, and this one is lengthy.
As a Lieutenant Jr. I served for a year on a large (>100m) ship, with the duties of assistant navigation officer, and of course, unofficial computer guy. When I first entered the ship (carrying my trusty laptop), I had to wait for 2 hours at the officer's wardroom... where I noticed an ethernet plug. After 15 minutes of waiting, I got bored. Like, really bored. What on TCP/IP could possibly go wrong?
So, scanning the network it is. Besides the usual security holes I came to expect in ""military secure networks"" (Windows XP SP2 unpatched and Windows 2003 Servers, also unpatched) I came along a variety of interesting computers with interesting things... that I cannot name. The aggressive scan also crashed the SMB service on the server causing no end of cute reactions, until I restarted it remotely.
But me and my big mouth... I actually talked about it with the ship's CO and the electronics officer, and promptly got the unofficial duty of computer guy, aka helldesk, technical support and I-try-to-explain-you-that-it-is-impossible-given-my-resources guy. I seriously think that this was their punishment for me messing around. At one time I received a call, that a certain PC was disconnected. I repeatedly told them to look if the ethernet cable was on. "Yes, of course it's on, I am not an idiot." (yea, right)
So I went to that room, 4 decks down and 3 sections aft. Just to push in the half-popped out ethernet jack. I would swear it was on purpose, but reality showed me I was wrong, oh so dead wrong.
For the full year of my commission, I kept pestering the CO to assign me with an assistant to teach them, and to give approval for some serious upgrades, patching and documenting. No good.
I set up some little things to get them interested, like some NMEA relays and installed navigation software on certain computers, re-enabled the server's webmail and patched the server itself, tried to clean the malware (aka. Sisyphus' rock), and tried to enforce a security policy. I also tried to convince the CO to install a document management system, to his utter horror and refusal (he was the hard copy type, as were most officers in the ship). I gave up on almost all besides the assistant thing, because I knew that once I left, everything would go to the high-entropy status of carrying papers around, but the CO kept telling me that would be unnecessary.
"You'll always be our man, you'll fix it (sic)".
What could go wrong?
I got my transfer with 1 week's notice. Panic struck. The CO was... well, he was less shocked than I expected, but still shocked (I learned later that he knew beforehand, but decided not to tell anybody anything). So came the most rediculous request of all:
To put down, within 1 A4 sheet, and in simple instructions, the things one had to do in order to fulfil the duties of the computer guy.
I. SHIT. YOU. NOT.
My answer:
"What I can do is write: 'Please read the following:', followed by the list of books one must read in order to get some introductory understanding of network and server management, with most accompanying skills."
I was so glad I got out of that hellhole.

This is my most ridiculous meeting in my long career. The crazy thing is I have witnessed this scenario play out many times during my career. Sometimes it sits in waiting for a few years but then BOOM there it is again and again. In each case the person that fell into the insidious trap was smart and savvy but somehow it just happened. The outcomes were really embarrassing and in some cases career damaging. Other times, it was sort of humorous. I could see this happening to me and I never want it to happen to you.

Once upon a time in a land not so far away there was a Kickoff Meeting for an offsite work area recovery exercise being planned for our Oklahoma locations. Eleven Oklahoma high ranking senior executives were on this webinar plus three Enterprise IT Directors (Ellen, Jim and Bob) who would support the business from the systems side throughout the exercise.

The plan was for Sam Otto, our Midwest Director of Business Continuity to host this webinar. Sam had hands-on experience recovering to our third party recovery site vendor and he always did a great job. He motivated people to attend the exercise with the coolest breakfasts and lunches you could imagine. Donuts, bagels, pizza, wings, scrumptious salads, sandwiches, beverages and desserts. He was great with people and made it a lot of fun.

At the last minute Charles 'Don't Call Me Charlie' Ego-Smith, the Global Business Continuity Senior Vice President, decided to grand-stand Sam. He demanded the reins to the webinar. Pulled a last-minute power-play and made himself the host and presenter. You have probably seen the move at some point in your career. I guess the old saying, 'be careful what you wish for' has some truth to it - read on and let me know if you devRanters agree...

So, Charlie, I mean Charles, begins hosting the session and greets all of the attendees. Hey, good so far! He starts showing some slides in the PowerPoint presentation and he fields a few questions, comments and requests from the Oklahoma executives. The usual easy to handle requests such as, 'what if we are too busy to do recover all systems', 'what if we recover all of our processes from home', 'what if we have high profile visitors that month?' Hey you can't blame them for trying. You are probably thinking to yourself, 'been there - heard that!' But luckily our experienced team had anticipated the push-back. Fortunately, Senior Management 'had our backs' and committed that all processes and systems must participate and test - so these were just softball requests, 'easy-peasy' to handle. But wait, we are just getting started!

Now the fireworks begin. Bob, one if the Enterprise IT directors started asking a bunch of questions. Well, Charles had somewhat of a history with Bob from previous exercises and did not take kindly to Bob's string of questions. Charles started getting defensive and while Bob was speaking Charles started IM'ing. He's firing off one filthy message after another to me and our teammate Sam.

'This idiot Bob is the biggest pain in the ass that I ever worked with'; 'he doesn't know shit', 'he never shuts the f up', 'I wanna go over to his office and kick his f'in ass...!'

Unfortunately...the idiot Charles had control of the webinar and was sharing his screen so every message he sent was seen by all of the attendees! Yeah, everyone including Bob and the Senior Oklahoma executives! We could not instant message him to stop as everyone would have seen our warnings, so we tried to call Charles' cell phone and text him but he did not pick up. He just kept firing ridiculously embarrassing dirty IM messages and I guess we were all so stunned we just sat there bewildered. We finally bit the bullet and IM'ed him to STOP ALREADY!!! Whoa, talk about an embarrassing silence!

I really felt sorry for Bob. He is a good guy. Deservedly, Charlie 'Yes I am going to call you CHARLIE' got in big time hot water after the webinar with upper management. For one reason or another he only lasted another year or so at our company. Maybe this event played a part in his demise.

So, the morale is, if you use IM - turn it off during a webinar if you are the host. If you must use it, be really careful what you say, who you say it to and pray nothing embarrassing or personal is sent to you for everyone to see.

Quick Update - During the past couple of months I participated on many webinars with enterprise software vendors trying to sell me expensive solutions. Most of the vendors had their IM going while doing webinars and training. Some very embarrassing things came flying across our screens. You learn a lot reading those messages when they pop-up on the presenters' screen, both personal and business related. Some even complaints from customers!

My advice to employees and vendors is to sign-out of IM before hosting a webinar. Otherwise, it just might destroy your credibility and possibly your career.

You write code.
A strange issue prevents you to proceed further.
Try one fix. Fails.
Try another Fix. Fails.
...
Try fix #28. Fails.
You decide to ask for help in the support forum.
You start writing your post, mentioning everything you've tried so far. You feel your social anxiety and fear the humiliation of being told "because you didn't try X, you idiot". Then you come up with an idea for fix #29.
(fix #29 normally involves Wireshark or similar low-level inspection tool)

Try fix #29. It succeeds :)

I was told in an 1:1, quite literally, "not everybody can do what they want to do if they are not good at it..." - get fucked! The person I had to "report to" was an idiot (at the same senior level as I was) and obviously threatened.

Then moved down to customer support, where I was fired for fixing problems faster than going through the chain of levels, because I was creating quick scripts to patch the faulty data.

Got this rude ass email from an idiot client who thinks I'm solely responsible for figuring out how to link his 3rd party email/newsletter sign up form to his new website without any access to the account. He "doesn't have the time to research". Newsflash asshat, I'm not responsible for your 3rd party shit. Go contact their support. 🙄😑

I hate being a fucking tech support dude. Everyone thinks it is my job to fix their device. Some girl asked me to replace her iPhone 6 plus screen a few days ago. I reluctantly said yes. I bought a screen. And I started the process. I opened the box for the new screen and it was just the screen with no digitizer. That was completely my fault. I was an idiot. I immediately buy the correct one on amazon and tell the girl, I'm sorry you won't have a phone for two days. As soon as the new package comes in, I will do the repair.
3 Days Later: Today.
Her: Has it come in yet?
Me: No, I'm going to call Amazon
Amazon: We're sorry, the thing you asked for was out of stock, you'll have to buy it again.
He was very nice, and he gave me free shipping, but this was not my fault!
Her: I have to wait 2 more days? That's like a whole week without a phone!
I had to do this for free and pay $40 for the new part. I am never telling anyone I am a developer again. I feel so fucking bad, and she's mad. And I can't do anything about it.

I hate working with egoistic noobshit hotshot "developers". But sadly, they tend to get ahead because they talk like they know everything in front of tech idiot management.

***

management: I need this swanky feature X in our product within the month.

me: That literally requires a huge refactor because our current codebase was never meant to support this type of service. We need to think about this.

noobshit: I disagree. This is easy. We're already doing something similar that is Z, this shouldn't take very long.

me: Z seems similar, but it actually quite different.

me (in my head): ... and you would know it's *completely* different if you fucking understood our own codebase vs what X needs you moron.

noobshit: Nah, it's similar. We can accomplish X if we polish up Z a bit.

*** 1 week later ***

noobshit: Omg X is horrifying and complex. We can't do it without a huge refactor.

me: yes

me (in my head): Fuck you

***

But guess who's got better career prospects because they're all shiny and positive in front of management?

I propose that the study of Rust and therefore the application of said programming language and all of the technology that compromises it should be made because the language is actually really fucking good. Reading and studying how it manages to manipulate and otherwise use memory without a garbage collector is something to be admired, illuminating in its own accord.

BUT going for it because it is a "beTter C++" should not constitute a basis for it's study.

Let me expand through anecdotal evidence, which is really not to be taken seriously, but at the same time what I am using for my reasoning behind this, please feel free to correct me if I am wrong, for I am a software engineer yes, I do have academic training through a B.S in Computer Science yes, BUT my professional life has been solely dedicated to web development, which admittedly I do not go on about technical details of it with you all because: I am not allowed to(1) and (2)it is better for me to bitch and shit over other petty development related details.

Anecdotal and otherwise non statistically supported evidence: I have seen many motherfuckers doing shit in both C and C++ that ADMIT not covering their mistakes through the use of a debugger. Mostly because (A) using a debugger and proper IDE is for pendejos and debugging is for putos GDB is too hard and the VS IDE is waaaaaa "I onlLy NeeD Vim" and (B) "If an error would have registered then it would not have compiled no?", thus giving me the idea that the most common occurrences of issues through the use of the C father/son languages come from user error, non formal training in the language and a nice cusp of "fuck it it runs" while leaving all sorts of issues that come from manipulating the realm of the Gods "memory".
EVERY manual, book, coming all the way back to the K&C book talks about memory and the way in which developers of these 2 languages are able to manipulate and work on it. EVERY new standard of the ISO implementation of these languages deals, through community effort or standard documentation about the new items excised through features concerning MODERN (meaning, no, the shit you learned 20 years ago won't fucking cut it) will not cut it.

THUS if your ass is not constantly checking what the scalpel of electrical/circuitry/computational representation of algorithms CONDONES in what you are doing then YOU are the fucking problem.

Rust is thus no different from the original ideas of the developers behind Go when stating that their developers are not efficient enough to deal with X language, Rust protects you, because it knows that you are a fucking moron, so the compiler, advanced, and well made as it is, will give you warnings of your own idiotic tendencies, which would not have been required have you not been.....well....a fucking idiot.

Rust is a good language, but I feel one that came out from the necessity of people writing system level software as a bunch of fucking morons.
This speaks a lot more of our academic endeavors and current documentation than anything else. But to me DEALING with the idea of adapting Rust as a better C++ should come from a different point of view.

Do I agree with Linus's point of view of C++? fuck no, I do not, he is a kernel engineer, a damn good one at that regardless of what Dr. Tanenbaum believes(ed) but not everyone writes kernels, and sometimes that everyone requires OOP and additions to the language that they use. Else I would be a fucking moron for dabbling in the dictionary of languages that I use professionally.
BUT in terms of C++ being unsafe and unsecured and a horrible alternative to Rust I personaly do not believe so. I see it as a powerful white canvas, in which you are able to paint software to the best of your ability WHICH then requires thorough scrutiny from the entire team. NOT a quick replacement for something that protects your from your own stupidity BY impending the use of what are otherwise unknown "safe" features.

To be clear: I am not diminishing Rust as the powerhouse of a language that it is, myself I am quite invested in the language. But instead do not feel the reason/need before articles claiming it as the C++ killer.

I am currently heavily invested in C++ since I am trying a lot of different things for a lot of projects, and have been able to discern multiple pain points and unsafe features. Mainly the reason for this is documentation (your mother knows C++) and tooling, ide support, debugging operations, plethora of resources come from it and I have been able to push out to my secret project a lot of good dealings. WHICH I will eventually replicate with Rust to see the main differences.

Online articles stating that one will delimit or otherwise kill the other is well....wrong to me. And not the proper approach.

Anyways, I like big tits and small waists.

I've worked in a lot of customer service jobs and the more i have to deal with client, the more story starting to pile up. But something always come back and it's frustrating. The entitlement people have. I work as a Technical Support agent and for the most part i'm actually happy to help people with fixing their problems. But once in a while i always get that idiot that doesn't do anything i told him, blame me because "my fixes" don't work or just straight up don't listen to me and think they know better. Why the fuck do you call me if you need help if you're going to ignore everything i say and act like a fucking children. I'm not the one that call for technical support.

I know this place is more for Dev, but i'm sure those kind of things happen all the time when a client think he know more than the dev themselves...

So. I was pretty sure I had fixed the problem we had with compiling in Windows 10. Thing is I did it in a stopgap non-permanent way because we have to be done with it by the second week of February to support our subcontractor.
Turns out I had an older version of the framework we build on installed on my box and the newer version decided to fix their windows 10 compilation issues the right way. So we can't use our stopgap solution. So basically I look like an idiot and more important people than me have to work on the problem because I am not allowed to install anything on my box myself, our SA is already overwhelmed, and only the higher ups have the newest framework version. Good thing it's a long weekend and I have plenty of of beer and whiskey.

First off murphy is a bitch. Week started off good, nothing bad happening then friday night came and i get an email about a site being down. Ok check it out real quick, cert is expired. No real big deal just a 20 minute fix, didn't bother me that i didn't get an expiry alert. Now is where murphy decided to be the biggest fucking bucktoothed cocksucker, generate a csr for a wildcard domain using an existing key and sent it off when i get it back the private key doesn't match the cert. Again ok maybe i fucked up, generate a selfsigned cert no fucking problem. Contact support to see if they have an idea. Oh now is when it gets fun, the fucking dumbass preceded to tell me how i didn't know what i was doing and how i just had to generate a csr and private key at the same time after i explained to the bastard that I've already tested it with a selfsigned cert. (How does this fucker have a job) By now apparently i was pissed off enough to scare murphy's pansy ass away cause i told the fucker to refund my money, got a list of 30 subdomains and setup letsencrypt on it. Now the part on this that is fucking hilarious is that it took me damn near 24 hours to be called a fucking idiot from a guy that doesn't know his ass between a hole in the fucking ground and 30 minutes of being pissed off more than i have been since i took anger management classes in the 9th grade to say fuck it and switch.

Idiot mode: on

It's bad when you realize you are the most idotic person you know. I just bought a wifi card replacement for my laptop only to find out that one of the screws on its back was completely unscrewable. I foolishly decided to force my way through by forcing the plastic. I tought I got away with it as I only damaged a plastic support tighten to the laptop base but now, my laptop screen isn't showing anything.

When I first booted it up after this, it was working, but it started showing troubling signs shortly after. Now, all I can get out of it is a completely black screen, no backlight at all.

What should I do? 😥

Imagine going on quora and answering somebodies carbon offsetting question by pushing your own stupid fucking agenda with propaganda answers like

"oh we need rainforest money!"

"oh we need grassland!"

"oh support the cows"

jesus fucking christ, THIS is why we have a problem with people not accepting climate change, becuase every fucking liberal wants to pile on one another and have their 'most important' cause behind it

give me a break you fucking idiots, it won't be solved by acting this way

sorry this is in no way software related, but it's the only place left i have to rant (however in some ways it is somehow software related, due to being able to think about the real world without being an absolute idiot and pushing some stupid peer pressured political idea because your social identity and friends are more important than actual facts, but whatever)

FML I am an idiot.. might end up in a rant here (well deserved!!) //if you are here reading this I'm so sorry again!!

I wrote to our support I need DP/HDMI cable.. they asked me to take a pic of the cable I'm currently using.. WTF?! Don't you know how connectors look?! Just get me the damn cable.. :/
Ok.. Took a picture.. sent it back.. At that time I still didn't see the problem with what I wrote/demanded..
Got back reply this is not HDMI connector... FML, I was so convinced computer had HDMI ports so even when I took the pic I wasn't paying attention.. Fuck.

And before when I was switching cables behind the computer below desk I was just blindly feeling around, it didn't even occurr to me to actually check what connectors are used..just knew both monitors had the same connector (and not aure why I thought HDMI :/)...so yeah, I'm the idiot who is not paying attention to stuff.. Fuck.. Was on a scavanger hunt for a wrong type of cable the whole time.. Sorry again!! And please don't kill me next time you see me.. o.O

So guys you all remember or know or will know how it is to be a student. Not that much money around, have to be responsible for the first time of your life and I don't know since we're all programmers here our Desktop/laptop that we invested our money on for the university is our life.

Recently I have found out that something is up with my laptop. My Ram should have been 8GB but it shows only 4. I almost fainted, I thought the seller caught an idiot (me) and sold it like that. So I decide, for some reason, to buy 2x8gb ram so I can have 16 since its the max support of the system.
I open the laptop and what to see but my laptop had 2x4gb in there.

Regardless I installed the new ones to find out what else but my PC is now showing just 8gb.

"Calm down Nick" I said maybe GPU uses it but no it only shows 4gb ram, the same amount the laptop came with so I guess it's integrated.

So now I can only think that the problem is occurred because my Father, dropped the laptop when I specifically told him to not have it in dangerous high places. I Googled around but everyone is talking just swaping the ram chips well yeah I did that 100 times, still the same.

Tl;Dr I'm freaking out because theres something up with my laptop

Okay, where do I even fucking start.

Today, my account been hacked by some prick because i wouldn't send him fucking nudes. I quickly emailed discord and they keep sending me automated emails. I got so fucking pissed and then they emailed me "how did they get your info?" BITCH HOW AM I SUPPOSED TO FUCKING KNOW? THATS WHY ITS CALLED HACKING IDIOT!

I sent them 5 fucking emails, no response.

Discord Support- Actually, DISCORD IN GENERAL IS A FUCKING HORRIBLE APP!

Message from discord: I am isabe*******@Gmail.com. I'm fucking pissed how your damn support team won't fucking just give my goddamn Discord account back. KEEP IN MIND I HAD A YEAR OF NITRO, A YEAR AND DISCORD CLEARLY DON'T GIVE A SHIT! YOU GUYS ARE SO FUCKING UNFAIR! LITERALLY YOU GUYS DON'T SOLVE ANY DAMN SITUATIONS WITHOUT IT TAKING MONTHS, OR YOU JUST DONT FUCKING REPLY!

I feel like such an idiot every time I use windows just slightly beyond clicking buttons. I'm trying to write a very simple macro to simply send an email out when I receive an email with a particular header. and no, outlook doesnt support that with rules. so now I have to use this garbage IDE, writing a script in a 25 year old language, with every bell and whistle button you could possibly think of and no way of figuring out how to do anything without being balls deep in a decade old forum post. I hate microsoft more and more every time I use it. I thought maybe if I got good and started "dev"ing with it more, I'd hate it less, but no... its always some super clunky application with shit tons of buttons and you dont know what they do, and when the app breaks, it gives you some hex number and nothing else, and sends all the good stuff to microsoft so they can fix it in the next "big update" thatll fuck up youre entire days worth of work and kill an hour of your precious time. Ugh.

I just had a discussion with a customer a week ago. He tould me that the PDF Files we are having in our application are not showing Up.
Connected to his computer to look at the problem just to find out That Google Chrome is blocking the popup. I tell him the problem and once He allows it to open it wont happen again.
Customer: I dont want That it also happens to my customers and they dont know that either. Just fix it and call me back" I try to explain him That we cant just change thr behaviour of the Browser but He already hung Up.
Well i guess we are going to buy Google the next week to change his Problem xD