Sit down before you read this.

So I interviewed a guy for a "Support Engineer" internship position.

Me and the team lead sit down and are waiting for him to enter, but apparently he's actually making a coffee in the kitchen.

This isn't exactly a strike since the receptionist told him that he can go get a drink, and we did too. It's just always expected for him to get a glass of water, not waste 3 minutes brewing a coffee.

In any case he comes in, puts the coffee on the table, then his phone, then his wallet, then his keys and then sits on our side of the table.
I ask him to sit in front of us so we can see him. He takes a minute to pack and tranfer himself to the other side of the table. He again places all of the objects on the table.

We begin, team lead tells him about the company. Then I ask him whether he got any questions regarding the job, the team or the company . For the next 15 minutes he bombards us with mostly irrelevant and sometimes inappropriate questions, like:
0: Can I choose my own nickname when getting an email address?
1: Does the entire department get same salaries?
2: Are there yoga classes on Sundays only or every morning?
3: Will I get a car?
4: Does the firm support workspace equality? How many chicks are in the team?
5: I want the newest grey Mac.

And then.. Then the questions turn into demands:
6: I need a high salary (asks for 2.5 more than the job pays. Which is still a lot).
I ask him why would he get that at his first job in the industry (remind you, this is an internship and we are a relatively high paying company).
He says he's getting paid more at his current job.
His CV lists no current job and only indicates that he just finished studying.
He says that he's working at his parent's business...
Next he says that he is very talented and has to be promoted very quickly and that we need to teach him a lot and finance his courses.

At this point me and the team lead were barely holding our laughs.

The team lead asks him about his English (English is not our native language).
He replies "It's good, trust me".
Team lead invites him for an English conversation. Team lead acts like a customer with a broken internet and the guy is there to troubleshoot. (btw that's not job related, just a simple scenario)
TL: "Hello, my name is Andrew, I'm calli..."
Guy: *interrupts* "Yes, yes, hi! Hi! What do you want?"
TL: "Well, if you let me fi..."
Guy: "Ok! Talk!"
TL: "...inish... My internet is not working."
Guy: "Ok, *mimics tuning a V engine or cooking a soup* I fixed! *points at TL* now you say 'yes you fixed'".

Important to note that his English was horrible. Disregarding the accent he just genuinely does not know the language well.

Then he continiues with "See? Good English. Told you no need to check!".

After about half a minute of choking on out silent laughter I ask him how much Python experience he has (job lists a requirement of at least 1 year).
He replies "I'm very good at object oriented functional programming".
I ask again "But what is your experience? Did you ever take any courses? Do you have a git repository to show? Any side.."
*he interrupts again* "I only use Matlab!".

Team lead stands up and proceeds to shake his hand while saying "we will get back to you".

At last the guy says with a stupid smile on his face "You better hire me! Call me back tomorrow." Leaves TL hanging and walks away after packing his stuff into the pockets.

I was so shocked that I wasn't even angry.
We both laughed for the rest of the day though. It was probably the weirdest interview I took part at.

Me: *hours of coding, develops a feature*
Code: I'm working..
Me: Oh good.. will monitor you for sometime.
Code: Ok, I'm done. I'll stop working now.
Me: WTF

Me: *sits for hours to solve bugs*
And when almost done,
VPN: Someone's having a good day, I'll disconnect you now.
Me: WTF

Me: *tries switching on/off VPN couple of times..*
When it starts to connect,
WIFI: Oh wait!! It's my turn to bid goodbye now. Have a nice day sir
Me: Of course !! The wifi

Me: *restarts router/ troubleshoot etc*
When wifi says connected...
Battery: Good job with wifi.. I'm down now..what you gonna do?
Me: Are you fucking kidding me???

Me: *connects charger, wait for laptop to switch on*
Windows: Updating....
Me: *jumps out window*

Sent an email out in work informing everyone that we had pushed updates out to all Windows PC's.

Got the following phone call 10 minutes later:

"Hi, I can't log into the banking account app on my iPhone. Did you do something to it with your updates?"

"Nope. They were PC updates."

"Well, I'm sorry but you're wrong. It must be you! It was working yesterday."

"Again, it's not us. What's the error message you're getting on your app?"

"Invalid password"

".....then could it just be that you're entering an invalid password?"

"No, I know the password. I only changed it yesterday!"

"So it was working before you changed the password?"

"That's what i said!
I'm telling you, it's your updates."

"Okay but before we go 'troubleshoot' it, how about ringing your bank firs-"

"Oh look, it doesn't matter if you don't want to help, I don't have time for this!
I'll ring your boss and he'll uninstall the updates for me and fix the app." *hangs up*

So my Girlfriend bought a new iPhone at Verizon today. Cool story, I know, but here's where it's gone from there.

Firstly her debit wouldn't run as credit, so we used mine but that's the least of it (but began it).

So she has 16,000 photos... Alot, sure, but not the issue. Obviously with that amount of data she wasn't about to reasonably use iCloud to back it up (understandable only by me) so she was confronted both by me and the Verizon employee about this issue to where we both (the Verizon employee and I) agreed that an iTunes backup/restore was the only way to preserve her data. She was confused. No worry, told her I had it handled and the Verizon employee agreed. Great. Yet we get home and begin the process. My girlfriend was not on the latest iOS (understandable given the battery scenario and she was on an iPhone 6) and this was ridiculous to her because she had to update in order to do the iTunes back up. Whatever, I brushed it off. Her phone was updated, and backed up... Which took a while but we are talking 30gb (of which she had no understanding of how much that was). After the back up we discovered her new phone wasn't working due to a bad sim, great, no problem we have the old one... But oh no. "I don't want that shitty old sim" she said. Uhmm what... I say, and say let me get an earring (to switch the Sims) and she gave one to me and as soon as I went to pop the tray, she had a fucking heart attack as if I was demolishing her phone. I talk her down, get it switched, get the phone to restore (slow process as she's complaining... 30gb mind you) and it works. She goes to bed. Comes back, texts aren't working. I say imessages or texts (now she has no idea) I troubleshoot, seems nothing's working, and that's okay Verizon must of reinstated the new sim and deactivated the old (fine). I switch them and it works. She proceeds to berate me about the SIM cards because she didn't want the 'old shitty one' (the one that got us to the place of a functioning phone).

Now everything works and she claims a Genius bar employee would of done this in minutes.

I (obviously) lose my shit, now I'm sleeping on the couch.

Im an IT professional / programmer..... this shit really ticked me off.

Worst dev team failure I've experienced?

One of several.

Around 2012, a team of devs were tasked to convert a ASPX service to WCF that had one responsibility, returning product data (description, price, availability, etc...simple stuff)
No complex searching, just pass the ID, you get the response.

I was the original developer of the ASPX service, which API was an XML request and returned an XML response. The 'powers-that-be' decided anything XML was evil and had to be purged from the planet. If this thought bubble popped up over your head "Wait a sec...doesn't WCF transmit everything via SOAP, which is XML?", yes, but in their minds SOAP wasn't XML. That's not the worst WTF of this story.

The team, 3 developers, 2 DBAs, network administrators, several web developers, worked on the conversion for about 9 months using the Waterfall method (3~5 months was mostly in meetings and very basic prototyping) and using a test-first approach (their own flavor of TDD). The 'go live' day was to occur at 3:00AM and mandatory that nearly the entire department be on-sight (including the department VP) and available to help troubleshoot any system issues.

3:00AM - Teams start their deployments
3:05AM - Thousands and thousands of errors from all kinds of sources (web exceptions, database exceptions, server exceptions, etc), site goes down, teams roll everything back.

3:30AM - The primary developer remembered he made a last minute change to a stored procedure parameter that hadn't been pushed to production, which caused a side-affect across several layers of their stack.

4:00AM - The developer found his bug, but the manager decided it would be better if everyone went home and get a fresh look at the problem at 8:00AM (yes, he expected everyone to be back in the office at 8:00AM).

About a month later, the team scheduled another 3:00AM deployment (VP was present again), confident that introducing mocking into their testing pipeline would fix any database related errors.

3:00AM - Team starts their deployments.
3:30AM - No major errors, things seem to be going well. High fives, cheers..manager tells everyone to head home.
3:35AM - Site crashes, like white page, no response from the servers kind of crash. Resetting IIS on the servers works, but only for around 10 minutes or so.
4:00AM - Team rolls back, manager is clearly pissed at this point, "Nobody is going fucking home until we figure this out!!"
6:00AM - Diagnostics found the WCF client was causing the server to run out of resources, with a mix of clogging up server bandwidth, and a sprinkle of N+1 scaling problem. Manager lets everyone go home, but be back in the office at 8:00AM to develop a plan so this *never* happens again.

About 2 months later, a 'real' development+integration environment (previously, any+all integration tests were on the developer's machine) and the team scheduled a 6:00AM deployment, but at a much, much smaller scale with just the 3 development team members.

Why? Because the manager 'froze' changes to the ASPX service, the web team still needed various enhancements, so they bypassed the service (not using the ASPX service at all) and wrote their own SQL scripts that hit the database directly and utilized AppFabric/Velocity caching to allow the site to scale. There were only a couple client application using the ASPX service that needed to be converted, so deploying at 6:00AM gave everyone a couple of hours before users got into the office. Service deployed, worked like a champ.

A week later the VP schedules a celebration for the successful migration to WCF. Pizza, cake, the works. The 3 team members received awards (and a envelope, which probably equaled some $$$) and the entire team received a custom Benchmade pocket knife to remember this project's success. Myself and several others just stared at each other, not knowing what to say.

Later, my manager pulls several of us into a conference room
Me: "What the hell? This is one of the biggest failures I've been apart of. We got rewarded for thousands and thousands of dollars of wasted time."
<others expressed the same and expletive sediments>
Mgr: "I know..I know...but that's the story we have to stick with. If the company realizes what a fucking mess this is, we could all be fired."
Me: "What?!! All of us?!"
Mgr: "Well, shit rolls downhill. Dept-Mgr-John is ready to fire anyone he felt could make him look bad, which is why I pulled you guys in here. The other sheep out there will go along with anything he says and more than happy to throw you under the bus. Keep your head down until this blows over. Say nothing."

It's maddening how few people working with the internet don't know anything about the protocols that make it work. Web work, especially, I spend far too much time explaining how status codes, methods, content-types etc work, how they're used and basic fundamental shit about how to do the job of someone building internet applications and consumable services.

The following has played out at more than one company:

App: "Hey api, I need some data"
API: "200 (plain text response message, content-type application/json, 'internal server error')"
App: *blows the fuck up

*msg service team*

Me: "Getting a 200 with a plaintext response containing an internal server exception"
Team: "Yeah, what's the problem?"
Me: "...200 means success, the message suggests 500. Either way, it should be one of the error codes. We use the status code to determine how the application processes the request. What do the logs say?"
Team: "Log says that the user wasn't signed in. Can you not read the response message and make a decision?"
Me: "That status for that is 401. And no, that would require us to know every message you have verbatim, in this case, it doesn't even deserialize and causes an exception because it's not actually json."
Team: "Why 401?"
Me: "It's the code for unauthorized. It tells us to redirect the user to the sign in experience"
Team: "We can't authorize until the user signs in"
Me: *angermatopoeia* "Just, trust me. If a user isn't logged in, return 401, if they don't have permissions you send 403"
Team: *googles SO* "Internet says we can use 500"
Me: "That's server error, it says something blew up with an unhandled exception on your end. You've already established it was an auth issue in the logs."
Team: "But there's an error, why doesn't that work?"
Me: "It's generic. It's like me messaging you and saying, "your service is broken". It doesn't give us any insight into what went wrong or *how* we should attempt to troubleshoot the error or where it occurred. You already know what's wrong, so just tell me with the status code."
Team: "But it's ok, right, 500? It's an error?"
Me: "It puts all the troubleshooting responsibility on your consumer to investigate the error at every level. A precise error code could potentially prevent us from bothering you at all."
Team: "How so?"
Me: "Send 401, we know that it's a login issue, 403, something is wrong with the request, 404 we're hitting an endpoint that doesn't exist, 503 we know that the service can't be reached for some reason, 504 means the service exists, but timed out at the gateway or service. In the worst case we're able to triage who needs to be involved to solve the issue, make sense?"
Team: "Oh, sounds cool, so how do we do that?"
Me: "That's down to your technology, your team will need to implement it. Most frameworks handle it out of the box for many cases."
Team: "Ah, ok. We'll send a 500, that sound easiest"
Me: *..l.. -__- ..l..* "Ok, let's get into the other 5 problems with this situation..."

Moral of the story: If this is you: learn the protocol you're utilizing, provide metadata, and stop treating your customers like shit.

So. A while ago I was on OkCupid, trying to find the Pierre to my Marie Curie (without the whole brain getting crushed under a horse carriage wheel obviously) and I decided the best way was to have my profile lead with my passion for technology. It turned out pretty unique, if I do say so myself.

At the end of it, I amassed some interesting and unique messages:

- A Java pickup line (that I never responded to. Yes I'm a very basic Devranter)

- A request to turn the man's software into hardware (to which I politely informed him that this was scientifically impossible unless a reader proves me wrong)

- Another impossible request to turn his floppy disk into a hard drive (how outdated too, why not HDD to SSD for faster speed amirite? That was awful don't mind me)

- A sincere request to help troubleshoot a laptop (Honestly I would've helped with help requests but this is a dating site...)

- A sincere request to help debug a student project followed with a link to a GitHub repo

- Another sincere request with studying for a computer exam

- And lastly, my favourite: a sincere job offer by a guy who went from flirtatious to desperate for a programmer in a minute. He was looking for *insert python, big data, buzzwords here* and asked me for a LinkedIn. I proceeded to inquire exactly what he wanted me to do. He then asks me to WRITE a Python tutorial and that he would pay a few cents per word written so he could publish it. Literally no programming involved.

Needless to say I went to look elsewhere.

Dev: “Ughh..look at this –bleep- code! When I execute the service call, it returns null, but the service received a database error.”
Me: “Yea, that service was written during a time when the mentality was ‘Why return a service error if the client can’t do anything about it?’”
Dev: “I would say that’s a misunderstanding of that philosophy.”
Me: “I would say it’s a perfectly executed example of a deeply flawed philosophy.”
Dev: “No, the service should just return something that tells the client the operation failed.”
Me: “They did. It was supposed to return a valid result, and the developer indicated a null response means the operation failed. How you deal with the null response is up to you.”
Dev: “That is stupid. How am I supposed to know a null response means the operation failed?”
Me: “OK, how did you know the operation failed?”
Dev: “I had to look at the service error logs.”
Me: “Bingo.”
Dev: “This whole service is just a –bleep-ing mess. There are so many things that can go wrong and the only thing the service returns is null when the service raises an exception.”
Me: “OK, what should the service return?”
Dev: ”I don’t know. Error 500 would be nice.”
Me: “Would you know what to do with error 500?”
Dev: ”Yea, I would look at the error log”
Me: “Just like you did when the service returned null?”
<couple of seconds of silence>
Dev: “I don’t know, it’s a –bleep-ing mess.”
Me: “You’re in the code, change it.”
Dev: “Ooohhh no, not me. The whole thing will have to be re-written. It should have been done correctly the first time. If we had time to do code reviews, I would have caught this –bleep- before the service was deployed.”
Me: “Um, you did.”
<a shocked look from Dev>
Dev: “What…no, I’ve never seen this code.”
Me: “I sat next to Chuck when you were telling him he needed to change the service to return null if an exception was raised. I remember you telling him specifically to pop-up an error dialog ‘Service request failed’ to the user when the service returned null.”
Dev: “I don’t remember any of that.”
Me: “Well, Chuck did. He even put it in the check-in comments. See…”
<check in comments stated Dev’s code review and dictated the service return null on exceptions>
Dev: “Hmm…I guess I did. –bleep- are you a –bleep-ing elephant? You –bleep-ing remember everything.”

<what I wanted to say>
No, I don’t remember everything, but I remember all the drive-by <bleep>-ed up coding philosophies you tried to push to the interns and we’re now having all kinds of problems I spend waaaaay too much time fixing.
<what I said, and lied a little bit>
Me: “No, I was helping Nancy last week troubleshoot the client application last week with the pop-up error. Since the service returned a null, she didn’t know where to begin to look for the actual error.”
Dev: “Oh.”

Person: You're good with computers right?
Me: Yes.
P: My computer won't boot after I unplugged it while trying to move it, how do I fix it?
M: I don't know
P: I thought you were good with computers
M: I am. Can't troubleshoot a computer with that little of info.
P: If I bring it to you will you fix it for me?
M: No.
P: What if burritos are involved?
M: I would consider it

This. This is how conversations should go when somebody asks us to fix their computer.

I'm a f****** idiot. Wifi adapter stopped working, I rebooted. I reinstall my distro. I look up for a replacement card. I troubleshoot the issue in software.

Finally someone says something one of the fourms.

I hit Fn + F2

It fucking works!!! The hardware was disabled by accident when I tried to open tty2.

FUCK!!!

With much help from a friend here (an unofficially related app, so I'm unsure of username here), I successfully dual booted my laptop to Arch Linux.

Tried Debian, but must have missed something, because it tried to format my whole SSD, which isn't good since my work software only works in windows.

Going to be a change, but I'm kind of excited. To the friend who helped me, I appreciate you and how late you stayed up to help me troubleshoot ❤

Online tutorial pet peeves
————————————

My top 10 points of unsolicited ranting/advice to those making video tutorials:

1. Avoid lots of pauses, saying “umm” too much, or other unnecessary redundancy in speech (listen to yourself in a recording)

2. If I can’t understand you at 1.5 - 2x playback speed and you don’t already speak relatively quickly and clearly, I’m probably not going to watch for long (mumbling, inconsistent microphone volume, and background noise/music are frequent culprits)

3. It’s ok to make mistakes in a tutorial, so long as you also fix them in the tutorial (e.g., the code that is missing a semicolon that all of a sudden has one after it compiles correctly — but no mention of fixing it or the compiler error that would have been received the first time). With that said, it’s fine to fix mistakes pertinent to the topic being taught, but don’t make me watch you troubleshoot your non-relevant computer issues or problems created by your specific preferences (e.g., IDE functionality not working as expected when no specific IDE was prescribed for the tutorial)

4. Don’t make me wait on your slow computer to do something in silence—either teach me something while it’s working or edit the video to remove the lull

5. You knew you were recording your screen. Close your email, chat, and other applications that create notifications before recording. Or at least please don’t check them and respond while recording and not edit it out of the video

6. Stay on topic. I’m watching your video to learn about something specific. A little personality is good, but excessive tangents are often a waste of my time

7. [Specific to YouTube] Don’t block my view of important content with annotations (and ads, if within your control)

8. If you aren’t uploading quality HD recordings, enlarge your font! Don’t make me have to guess what character you typed

9. Have a game plan (i.e., objectives) before hitting the record button

10. Remember that it’s easier to rant and complain than to do something constructive. Thank you for spending your time making tutorial videos. It’s better for you to make videos and commit all my pet peeves listed above than to not make videos at all—don’t let one guy’s rant stop you from sharing your knowledge and experience (but if it helps you, you’re welcome—and you just might gain a new viewer!)

"Whenever a user creates their account, they get an email with their password. We also get a copy of said email which makes it easy to troubleshoot any issues when they ring us." -- I was so tempted to hand in my resignation on the spot...

How to troubleshoot when running low on time:
- Google issue
- Open Stack Overflow link
- Scroll past question details and straight to answer.
- Pray question was relevant

That moment someone stands over your shoulder to help you troubleshoot and your mind becomes that of a 4 year old...

Windows troubleshooting:
- Works on my system, therefore it's not an issue.
- Must be a hardware error.
- Obviously it's just cheap hardware.
- Have you tried turning it off and on again?
- Here's some obscure error code that leads nowhere.
- Have you tried "sfc /scannow"?
AS IF SFC IS A FUCKING SILVER BULLET!!!
- Our Indian support chap from answers.microsoft.com will help you.

RRRREEEEEEEEEEEEE!!!!!!!
Solution: quietly weep and reinstall your system.

Linux troubleshooting:
- There are good quality log files.
- You can run the program from the command-line and read both stdout and stderr from it.
- You can usually run the program with high verbosity options to help you track down the error.
- Even daemons can have their commands spawned from a dedicated shell, to see why they failed.
- Usually it's a configuration error and you can easily edit the configuration file.
- More often than not, the program will tell you why it failed.

Solution: usually easy to find.

I fucking love Windows. Because you know, it's so easy to troubleshoot and the support is so great!!!

We can compile, transpile, and do all sorts of fucky internet things through an entire development pipeline and then troubleshoot through all sorts of hackery and dev sorcery to output html.

Or I can just index.php and be done with it.

I dunno man, I dig frontend and using the popular js libs to put shit online and be done without having to deal with the fuckery that is wasm or use something similar to Rust to bring shit to my clients.

9 times out of 10, these dudes have been well served with the php or node or even golang that i give them.

Seems that a lot of tools coming up just make shit harder.

Even VBScript seems simpler compared to the amount of web fuckery going on right now.

Yeah I keep current, but fuck, every day it seems as if shit was just getting more and more complex

I worked at a computer store for almost 4 years, don’t really have any seniors since the first year and if I don’t understand something google are my only hope

So during 4th year it got worse, I got college final project also tons of work. That last year really burn me out like crap. No one’s complaining if I can’t troubleshoot something (even the boss or client) but I feel depressed if I failed to help them

I quite 3 months ago and currently on another city with a software company, first 2 months was great, tons of senior and I can finally rely on someone instead of pulling my hair by myself

P.S. The store working atmosphere was nice, but I just don’t wanna be last man when shit happens. Especially if it’s my 1st job

So I just found out that my colleague who I often have to work with does not use a debugger to troubleshoot any bugs at all. Actually, he does not even run or test his code locally either with prints or something similar. He just commits java code directly on bitbucket, no source control, without making sure it compiles and then he runs a CI provided by devops that takes 4 freaking hours to run because he bloated that shit up somehow.

I suggested politely to help him find a more efficient approach and to use my hardware setups for speeding up his work because I assume it must be pretty painful to work with, but he just refused.

That and those "seniors" with 10 years Linux development XP in the embedded field who don't know basic commands like ls, cat and touch and code in notepad.

Fucking me, who the hell am I working with and can someone please end me?

So my friends PC died, since he lives in another country I help him over Signal.

He assembled his own PC a year ago and does a lot of programming for his study. Today Im helping him troubleshoot why his pc does not boot. Does it get into the bootmenu or not? He knows it doesnt. Then I recommend him to try unplugging his graphics card and plug his monitor in the motherboard. I then get a question if there are two HDMI types. Im smiling and think he is messing with me. That must be a displayport. Nope he was serious, he has this HDMI cable that doesnt fit his motherboard.

I sat in a tram and laugh out loud.. Because this is what he send me.
If it was anyone who didnt do anything with computers I didnt think it was laughable, but come on every programmer should know the difference between HDMI and DisplayPort

Biggest challenge I overcame as dev? One of many.

Avoiding a life sentence when the 'powers that be' targeted one of my libraries for the root cause of system performance issues and I didn't correct that accusation with a flame thrower.

What the accusation? What I named the library. Yep. The *name* was causing every single problem in the system.

Panorama (very, very expensive APM system at the time) identified my library in it's analysis, the calls to/from SQLServer was the bottleneck

We had one of Panorama's engineers on-site and he asked what (not the actual name) MyLibrary was and (I'll preface I did not know or involved in any of the so-called 'research') a crack team of developers+managers researched the system thoroughly and found MyLibrary was used in just about every project. I wrote the .Net 1.1 MyLibrary as a mini-ORM to simplify the execution of database code (stored procs, etc) and gracefully handle+log database exceptions (auto-logged details such as the target db, stored procedure name, parameter values, etc, everything you'd need to troubleshoot database errors). This was before Dapper and the other fancy tools used by kids these days.

By the time the news got to me, there was a team cobbled together who's only focus was to remove any/every trace of MyLibrary from the code base. Using Waterfall, they calculated it would take at least a year to remove+replace MyLibrary with the equivalent ADO.Net plumbing.

In a department wide meeting:

DeptMgr: "This day forward, no one is to use MyLibrary to access the database! It's slow, unprofessionally named, and the root cause of all the database issues."
Me: "What about MyLibrary is slow? It's excecuting standard the ADO.Net code. Only extra bit of code is the exception handling to capture the details when the exception is logged."
DeptMgr: "We've spent the last 6 weeks with the Panorama engineer and he's identified MyLibrary as the cause. Company has spent over $100,000 on this software and we have to make fact based decisions. Look at this slide ... "
<DeptMgr shows a histogram of the stacktrace, showing MyLibrary as the slowest>
Me: "You do realize that the execution time is the database call itself, not the code. In that example, the invoice call, it's the stored procedure that taking 5 seconds, not MyLibrary."
<at this point, DeptMgr is getting red-face mad>
AreaMgr: "Yes...yes...but if we stopped using MyLibrary, removing the unnecessary layers, will make the code run faster."
<typical headknodd-ers knod their heads in agreement>
Dev01: "The loading of MyLibrary takes CPU cycles away from code that supports our customers. Every CPU cycle counts."
<headknod-ding continues>
Me: "I'm really confused. Maybe I'm looking at the data wrong. On the slide where you highlighted all the bottlenecks, the histogram shows the latency is the database, I mean...it's right there, in red. Am I looking at it wrong?"
<this was meeting with 20+ other devs, mgrs, a VP, the Panorama engineer>
DeptMgr: "Yes you are! I know MyLibrary is your baby. You need to check your ego at the door and face the facts. Your MyLibrary is a failed experiment and needs to be exterminated from this system!"

Fast forward 9 months, maybe 50% of the projects updated, come across the documentation left from the Panorama. Even after the removal of MyLibrary, there was zero increases in performance. The engineer recommended DBAs start optimizing their indexes and other N+1 problems discovered. I decide to ask the developer who lead the re-write.

Me: "I see that removing MyLibrary did nothing to improve performance."
Dev: "Yes, DeptMgr was pissed. He was ready to throw the Panorama engineer out a window when he said the problems were in the database all along. Didn't you say that?"
Me: "Um, so is this re-write project dead?"
Dev: "No. Removing MyLibrary introduced all kinds of bugs. All the boilerplate ADO.Net code caused a lot of unhandled exceptions, then we had to go back and write exception handling code."
Me: "What a failure. What dipshit would think writing more code leads to less bugs?"
Dev: "I know, I know. We're so far behind schedule. We had to come up with something. I ended up writing a library to make replacing MyLibrary easier. I called it KnightRider. Like the TV show. Everyone is excited to speed up their code with KnightRider. Same method names, same exception handling. All we have to do is replace MyLibrary with KnightRider and we're done."
Me: "Won't the bottlenecks then point to KnightRider?"
Dev: "Meh, not my problem. Panorama meets primarily with the DBAs and the networking team now. I doubt we ever use Panorama to look at our C# code."

Needless to say, I was (still) pissed that they had used MyLibrary as dirty word and a scapegoat for months when they *knew* where the problems were. Pissed enough for a flamethrower? Maybe.

TLDR: There’s truth in the motto “fake it till you make it”

Once upon a time in January 2018 I began work as a part time sysadmin intern for a small financial firm in the rural US. This company is family owned, and the family doesn’t understand or invest in the technology their business is built on. I’m hired on because of my minor background in Cisco networking and Mac repair/administration.

I was the only staff member with vendor certifications and any background in networking / systems administration / computer hardware. There is an overtaxed web developer doing sysadmin/desktop support work and hating it.

I quickly take that part of his job and become the “if it has electricity it’s his job to fix it” guy. I troubleshoot Exchange server and Active Directory problems, configure cloudhosted web servers and DNS records, change lightbulbs and reboot printers in the office.

After realizing that I’m not an intern but actually just a cheap sysadmin I began looking for work that pays appropriately and is full time. I also change my email signature to say “Company Name: Network Administrator”

A few weeks later the “HR” department (we have 30 employees, it’s more like “The accountant who checks hiring paperwork”) sends out an email saying that certain ‘key’ departments have no coverage at inappropriate times. I don’t connect the dots.

Two days later I receive a testy email from one of the owners telling me that she is unhappy with my lack of time spent in the office. That as the Network Administrator I have responsibilities, and I need to be available for her and others 8-5 when problems need troubleshooting. Her son is my “boss” who is rarely in the office and has almost no technical acumen. He neglected to inform her that I’m a part time employee.

I arrange a meeting in which I propose that I be hired on full time as the Network Administrator to alleviate their problems. They agree but wildly underpay me. I continue searching for work but now my resume says Network Administrator.

Two weeks ago I accepted a job offer for double my current salary at a local software development firm as a junior automation engineer. They said they hired me on with so little experience specifically because of my networking background, which their ops dept is weak in. I highlighted my 6 months experience as Network Administrator during my interviews.

My take away: Perception matters more than reality. If you start acting like something, people will treat you like that.

Sitting in my backyard, trying to mentally troubleshoot some coding issues in the fresh air, and I hear my neighbor say, "...she was picking her bum before..."

Back inside I go.

When I started my current job 6 years ago I was given a desk phone with a 100mb port. Speed didn't matter at the time as everyone was given laptops for our desks. I changed positions in the company where I'm going to be provisioning servers and whatnot over the network. Started using a desktop that didn't have a Wi-Fi adapter. I requested a new phone with a Gig switch port, if possible, so doing file transfers on the network wouldn't be limited. IT had a couple of questions...

IT-Have you noticed slowness when downloading/uploading?
Me-No, but its a 100mb port...so.
IT-Well I just did a speed test and we're getting 60up/5down. Your phone is over that.
(Working from home? Our fiber was way faster than that I thought.)
Me-That's fine, but this will be for internal network transfers. Not going out to the internet. We have gigabit switches on campus correct?
It-Yes but you shouldn't notice a speed difference.
Me, now lost-If you can't change out the phone that's fine. I'll figure our something.
IT-Now now, lets troubleshoot your issue. Can you plug your phone in?
Me-Yes I have it, but I'm remote today. There is no way for it to reach the call manager.
IT-Let's give it a try.

40 min of provisioning later he gave up and said maybe it is broke. Got a "working" one the next week.

PS first post, and writing on phone. Yay insomnia!

I finally fucking did it!

I strapped up, strapped in, strapped on... uh wait what?

I finally made the full dedicated switch to linux on my personal computer. Blew away Windows and installed linux. I was able to get about 95% of the games that I actually play on PC to run under a combo of proton/lutris-wine.

I feel like after working in a (primarily) linux shop for almost 2 years now, I've learned enough to be able to actually troubleshoot if/when something goes wonky. I've been a windows/sysadmin type in my career for about 8 years and only touched small bits of linux here and there or for fun little projects like a retropie setup.

But thanks to this gig I'm working at now, as a devops engineer, I've learned so got'damn much about linux and I've been developing scripts/tools that run on linux I figured I could, or better yet 'should', take the full plunge.

So, I've decided that if there's something I absolutely need on Windows that Linux doesn't support, instead of knee-jerking and going back to Windows, I'm going to just setup a VM of windows and daily drive Linux from now on.

Some gfx tweaks for games were definitely necessary, it's still not quite as plug and play as Windows for games, but the fact that it only took like 1.5 hours to sort out all of my games performance is really impressive. Especially, considering none of these games actually supports linux out of the box and Wine/Proton is being used to get them to work.

Should a developer really have to be a jack of all trades? I write code, but at work I feel like I am always getting pulled into sysadmin debacles. I am not a sysadmin or an ops person. I am a developer, not a systems guy.

If you want me to be a systems guy, then train me to be one. You hired me to write code, not to troubleshoot shitty IBM Application Servers.

But what the FUCK VULTR!!!
It is the third time in two weeks that I actually have to reopen issues because your staff do not know how to troubleshoot correctly!

If there is routingproblems, please check from an external server and not from the same network!

I dont know, but Vultr has significantly lost the servicemind during this year...
Time for another host?

Our website stopped working. A coworker said her guess from an error she saw in the logs was that it might have something to do with a bit of a commented line in .htaccess taking itself out of comment and into code due to a specific set of characters the line contained. I looked at .htaccess and thought “Nah, that can’t be it.” and proceeded to troubleshoot pretty much everything but that. After 30 minutes my coworker opened the file and fixed the comment and all was well. I felt stupid because on our team I’m supposed to be the expert that figures out stuff like this.

Aren't the system admin supposed to figure out how to install something on their server when a developer has requested something from them?

They seem to have no idea when I request them to install php gd extension. They also cannot give me a ssh access to their server. So I have to troubleshoot/help by sending one command and ask for the output from them and give another command to run through mail.

I don't even know what to rant or whom to rant at anymore.

// I'm blue.

A vendor gave us what is turning out to be a very stable storage appliance/software, so we're happy for that. But even so, disks fail. So we need an automated way to identify, troubleshoot, isolate, and begin ticketing against disk failures. Vendor promised us a nice REST API. That was six months ago. The temporary process of SSHing(as root) to every single appliance(60-200 per site, dozens of sites) to run vendor storage audit commands remains our go-to means of automation.

Best: Defeating a seasoned IT professional who was unable to troubleshoot a problem for a week and me doing it in 25 minutes.

Worst: Dealing with anxiety and programmer's block.

Had an internet/network outage and the web site started logging thousands of errors and I see they purposely created a custom exception class just to avoid/get around our standard logging+data gathering (on SqlExceptions, we gather+log all the necessary details to Splunk so our DBAs can troubleshoot the problem).

If we didn't already know what the problem was, WTF would anyone do with 'There was a SQL exception, Query'? OK, what was the exception? A timeout? A syntax error? Value out of range? What was the target server? Which database? Our web developers live in a different world. I don't understand em.

Still dealing with the web department and their finger pointing after several thousand errors logged.

SeniorWebDev: “Looks like there were 250 database timeout errors at 11:02AM. DBAs might want to take a look.”

I look at the actual exceptions being logged (bulk of the over 1,600 logged errors)..

“Object reference not set to an instance of an object.”

Then I looked the email timestamp…11:00AM. We received the email notification *before* the database timeout errors occurred.

I gather some facts…when the exceptions started, when they ended, and used the stack trace to find the code not checking for null (maybe 10 minutes of junior dev detective work). Send the data to the ‘powers that be’ and carried on with my daily tasks.
I attached what I found (not the actual code, it was changed to protect the innocent)
Couple of hours later another WebDev replied…

WebDev: “These errors look like a database connectivity issue between the web site and the saleitem data service. Appears the logging framework doesn’t allow us to log any information about the database connection.”

FRACK!!...that Fracking lying piece of frack! Our team is responsible for the logging framework. I was typing up my response (having to calm down) then about a minute later the head DBA replies …

DBA: “Do you have any evidence of this? Our logs show no connectivity issues. The logging framework does have the ability to log an extensive amount of data regarding the database transaction. Database name, server, login, command text, and parameter values. Everything we need to troubleshoot. This is the link to the documentation …. If you implement the one line of code to gather the data, it will go a long way in helping us debug performance and connectivity issue. Thank you.”

DBA sends me a skype message “You’re welcome :)”

Ahh..nice to see someone else fed up with their lying bull...stuff.

Printers have always bothered me because I haven’t known how to troubleshoot them.
Today I changed that. I reconfigured my printer and fixed the printer connections on my home computers.

Still hate printers though.

May or may not have just spent 10 minutes trying to troubleshoot why my terminal couldn't find nano only to realise I'm on a windows PC after every other command i tried failed...

I'm out of my comfort zone, send flannelette and help!

I JUST HAD ONE OF THOSE DAYS THAT MAKES ONE WANT TO BANG TWO BRICKS ON HEAD SND END THE PAIN THE STORY STARTS YESTETDAY WITH ISSUES AFTER A MIGRSTION AND THEY ASK ME TO HELP TROUBLESHOOT EVEN THOUGH I'M A DEV DBA AND THE ISSUE IS IN QA/SAT AND I HELP ANYWAY AND THEY CAN'T FIND A VIEW AND SO I LOOK EVERYWHERE AND CAN'T DOING IT EITHER AND IT DIDN'T EXIST IN PROD OR DEV SO I TELL THEM IT'S NOT THERE, AND THEY ARE LIKE, CAN YOU RETRIEVE IT FOR US AND I'M LIKE FROM WHERE? I DON'T KEEP VIEWS IN MY BUTT AND YOU GUYS ARE SMOKING CRACK AND THE GIVE ME THEIR QUERY WHICH CONTAIN THE VIEE ANYWAY AND THEY SAY CAN YOU RUN IT AND IT RUNS AND WORKS AND THEY CAN'T MAKE IT WORK AND IT WORKS BECAUSE IT DOESN'T CALL THE VIEW THEY HAVE ME SO NO PROBLEM THERE SO I FINALLY ASK THEM ARE YOU POINTING TO THE CORRECT DATABASE AND THEY'RE LIKE OH MAN WE TOLD YOU THE WRONG DATABASE AND SO I LOOK AT THE RIGHT DATABASE AND FIND THAT THE GRANTS ARE MISSING AND YEAH THANK YOU FOR TAKING EIGHT HOURS OF MY LIFE BECAUSE WE WERE IN THE WRONG DB YOU GAVE ME AND I HOPE THE FLAG OF A THOUSAND CAMELS INVEST YOUR ARMPITS AND THE CHIGGERS OF A THOUSAND SOUTHERN LAWNS INGEST YOUR SOCKS AND UNDERWEAR. YAAAAAA!!!!

Not been a good day so far:
1. Woke up to my Synology in a 'Volume crashed' state. Tried to contact support via web page; support web page not loading.
2. Ancient software at work stops working. As the last remaining C++ dev, I gotta troubleshoot. Original developer wrote test program...in VB6.
3. Server config file changed, but all the admins swear up and down nobody's made any changes.
4. Client calls account rep and wants to know about our security policies, so he schedules a meeting with me and client and forgets to mention until he's emailing me asking where the hell I am. From the tone of the conversation between the rep and the client, it's clear that somehow I'm to blame for being late.

Sigh.

Well, hey, at least it's Friday, right? Right?

So recently I completed side gig from random freelancing site where I had to shadow troubleshoot performance problems over teams call with random Indian guy on his client's AWS account. Long story short you can autoscale new instances all you want but it's not gonna help if your FIFO sqs has only one message group ID. This architecture is running an online game, which is basically limited to processing ONE event at the same time for ALL players xD
What's even better, basing on naming convention I realized it's a company that I interviewed for like 4 months ago and they told me "we need someone with more experience". Well good luck, thanks for quick cash

When your non-programmer boss asks how exactly some code/bug was fixed.

"You sure? I mean, alright... "

It's not like every time something doesn't work right, this will be the fix. We're not going to have a conversation in the future where you help me troubleshoot something by remembering parts of this conversation.

Sorry I'm on my computer during the meeting but I can multitask I swear!

(I can definitely write code and troubleshoot with other devs on Skype, while you're talking)
I never said I was listening to you though! Lol!

Long story short, my mama fixed the printer!

Well, more like she did troubleshoot.
Needed to print something and printer didn’t light up. Did some basic troubleshooting but didn’t work. So assumed it’s spoiled and thought would just use softcopy since document isn’t that important.

When papa told mama abt it, she went ahead and troubleshoot/setup for me to print. Even printed out a test doc, lol.

Then she remarked, “u’ve been doing software, that’s why not so good with hardware hah!”

Proud child is proud. 💪🏿

Client contacts our company that his site is down, we do some investigating and the only way we can access the site is on a mobile phone. From the office computers the site never loads and times out. Since we don't host the site and I've never logged into it before I don't have a lot of details so I suggest they contact whoever hosts their site. This is where things get weird.

Client tells me that the site is hosted on someone's home server. I tell him that this is quite strange in 2018 and rather unlikely and ask if he was ever given access to the site to log in or if he has access to his domain registration, GoDaddy.

He says he doesn't understand any of this and would rather I just contact his current developer and figure it out with him. We agree that he needs to get access to his site so we are going to migrate it once I get access to it.

I email his current developer letting him know the client has put me in contact with him to troubleshoot the issues with the site. I ask him some standard questions like: where is the site hosted? Can you access it from a computer? Do you have some security measures in place to block certain IP ranges? Can you give me from access to get the files? Will you send me a backup of the site for me to load up on my server?

*2days pass*

Other dev: Tell me the account number and I'll transfer the domain.

Me: I'll have to get back to you on that once I talk to the client and set up his GoDaddy account since we believe the business owner should own their domain, not their developers. In the meantime you didn't answer any of the questions I asked. Transferring the domain won't get the site on my server so I still need the files.

*3 days pass*

OD: You are trying the wrong domain. The correct domain is [redacted].com I'll have my daughter send you the files when she gets in town. We will transfer the domain to you, the client will forget to pay and the site will go down and it'll be your fault.

Me: I appreciate your advice, but the client will own their domain. I'm trying to get the site online and you have no answered any of my questions. It's been a week now and you have not transferred the domain, you have not provided a copy of the site, you have not told me where the site is hosted. The client and I are both getting impatient at this point when will we receive a backup of the site and the transfer of the domain?

OD: Go fuck yourself, tell the client they can sue me.

If the client is that terrible, wouldn't you want to hand them off to anyone willing to take them? I have never understood why developers and agencies try to hold clients hostage by keeping their domain or website and refusing access. From what I can tell this is a freelance developer without a real company so a legal battle likely isn't going to go well since the domain is worthless to him as the copyright to the name is owned by the client. This isn't the first time we've had to help clients through this sort of thing.

Story time:

I worked at a firm that had an infernal off the shelf CRM system that they collaborated with the dev company to customise.

They were seriously behind the competition, and didn’t have any app or web presence for interacting with their system, instead relying on people calling (fine for the nature of the business, but competition was leaving them in the dust).

They decided that they needed to redevelop it in-house, with a focus on supporting the web and apps.

I was hired for this purpose.

It was me and one other dev, who was also the head of IT.

He’d built a small prototype, and was new to the whole WPF / MVVM thing for the in-house app, so with my previous experience it was clear it needed to serve as an example only, and that it would need redeveloping.

I was only there three months.

In that time I singularly (he was pulled away to troubleshoot their VOIP installation - yes, for three months as other companies kept dropping the ball) built:

- A WebAPI with JWT auth
- An MVC skeleton frontend
- A WPF desktop app

It had all sorts of cool shit in it, 2FA, Reactive UI, Reactive extensions, server push to desktop, a custom workflow and permissions system.

It was pretty dang cool.

End of the three months rolled around, and the non-technical managers were concerned about time to market, so they decided to drop me as I’d “not made enough progress”.

I’d also had a bit of absence which they were aware of and were supposedly supporting me through.

But MFW three months is assumed to be enough time to build such a system with one dev.

A service had/has been logging hundreds of errors in the development environment and I reached out to the owning process mgr that the error was occurring and perhaps a good opportunity to log additional data to help troubleshoot the issue if the problem ever made its way to production. He responded saying the error was related to a new feature they weren't going to implement in the backing dev database (TL;DR), and they know it works in production (my spidey sense goes off).
They deployed the changes to production this morning and immediately starting throwing errors (same error I sent)
Mgr messaged me a little while ago "Did you make any changes to the documentation service? We're getting this error .."

50% sure someone misspelled something in a config, but only thing they are logging is 'Unable to parse document'. Nothing that indicates an issue with the service they're using.

Just came back from vaccation yesterday. During sprint retrospective today I hear my team was having trouble dealing with the API layer (which was mostly written by me). Suggestion was a session where I sit and explain the application to the team ,which I have no problem with.

One of my teammates asserts that it's written in such a way that "only the person who wrote it can modify it".

Agree to disagree but whatever. This thing goes through code review everytime I push changes to it. If there was a problem I don't know why he's just discovering it 6 months into the project. I assure you there's no rocket surgery going on. The problem is that I have been doing everything on that side of the project and nobody was curious enough to give it a read sometime. In fact I dont think anything needed to change while I was on vacation, they just didn't have me to troubleshoot every problem for them like usual 😤

I'd like to give a shoutout to the best tool I ever had when I worked in hardware and had to troubleshoot ethernet. The "RLFLTWKW". (The Really Long Fly Lead That We Know Works)

My friend that I worked with long ago just dug it out of a drawer and sent me a photo so we could remember the days when trying to figure out why Mavis couldn't get on the network anymore could be resolved by our faithful friend "TRLFLTWKW". I miss you buddy. You made life so much better.

I wish I had an equivalent to you for coding.

When you ask your infrastructure admins for a firewall rule and you are very specific. They say that you don't need it... you troubleshoot for 2 hours then argue with them for 5 hours. Then they add the rule and it works. I want to punch someone right now and have a beer. FML!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

one of my guys decided to start learning c++ for the fun and fuck of it. We do not use c++ for shit (we web developers in this bitch) and he asked me if in the event of him getting completely fucking stuck he could come to me for guidance, I said sure. I do use c++ for personal game projects....it is mostly very bad C until I need c++, it is horrible seriously, I ain't no expert.

He decides to go with the LLVM. Creates a simple hello world app. Runs clang++ main.cpp -o main.

**QUICK PAUSE**

Done, the CLI returns the prompt back to him. He comes and asks me wtf is going on. I check on my machine(Linux based) and do the exact same thing. Executable comes out.

I check back on his windows machine, try typing the same shit. Nada. It does not throw errors or warnings, and the syntax is fucking fine, can't really fuck up c-outing hello fucking world. FUCKING NADA

I couldn't sit down to troubleshoot since it was still working hours, but this shit is haunting me and I am going ballsack crazy knowing that I won't be able to jump at it until tomorrow.

This just makes me dislike c++, i usually never have issues like that, but then again, I use the microsoft compiler (bitch at me all you want, most game developer tutorials etc use that shit, so does the Cherno, its all i know OK????)

I am going to go crazy sdjkfhasdkjlfghlajkhrfvluidefjbhfksjadhjksdsdsjksdjkl

When two people who don't know shit about computers start trying to troubleshoot each others' problems

What follows is an email I want to send very badly right now:

RE: please provide new date format

There is no new date format. You have the day and month switched. In the sample you've provided.

You've been getting away with it up til now because the digits were small enough to be either a month or day.

Then, as soon as you hit a snag you immediately gave up and assumed it was me changing things. You came to me before even making a guess what could be wrong.

Learn to fucking troubleshoot PLEASE. I am sick of your lazy shit coming to me with an issue every time you stub your toe. You are professional developers and I am your junior.

That moment when the bug you are trying to troubleshoot isn't a bug but rather the result of a feature you wrote that actually fucking works!

How many problems can one project have? You name it I bet I have seen it and had to troubleshoot it in the last month.

So I'm working our remote build/testing server, and all of a sudden my computer just turns off. No crash message, no error, just turned off. My co-worker tries to help troubleshoot the problem.

Nothing.

I take the computer downstairs to the hardware department. They plug it in and it starts no problems.

After it finishes updating, I take it back upstairs and plug it back in.

Nothing.

I suggest that it is the power cable, and my co-worker looks under his desk. Turns out he had kicked the switch on the surge protector. 😑

I hate it when a family member ask me to fix something and I fold and try and fix it. I start to troubleshoot and they see what I'm doing and say "oh I thought you knew how to fix it, NVM I can do it." Like wtf this is how u fix stuff

1) Never be afraid to ask questions.

There are so many instances of situations where assumptions have been made that shouldn’t have been made, resulting in an oversight that could have been rectified earlier in a process and wasn’t.

Just because no one’s asking a question doesn’t mean you’re the only person who has it.

That being said, it’s really important to figure out how to ask questions. Provide enough context so that the audience for your question understands what you’re really asking. If you’re trying to troubleshoot a problem, list out the steps you’ve already tested and what those outcomes were.

2) When you’ve learned something, try to write about it. Try to break it down as though you were explaining it to a child. It’s through breaking down a concept into its most simple terms that you really know that you understand it.

3) Don’t feel like you have to code *all of the time*. Just because this is what you’re doing for a living doesn’t mean that you have to make it your life. Burnout is real, and it happens a lot faster if it’s all you do.

4) Find hobbies outside of tech!

5) Network. There are a number of great communities. I volunteer for and am a member of Virtual Coffee, and can vouch for that community being particularly friendly and approachable.

6) Don’t let a company pay you less than industry standard and convince you that they’re doing you the favor of employing you.

7) Negotiate salary. Always.

8) If you’re a career transitioner, don’t be afraid to talk about your previous work and how it gave you experience that you can use in programming. There’s a whole lot of jobs that require time management, multi-tasking, critical thinking, etc. Those skills are relevant no matter where you got them.

9) If it takes a while for you to get a gig, it’s not necessarily a reflection on you or your abilities.

10) Despite what some people would say, coding’s not for everyone. Don’t feel like you have to continue down a road just because you started walking down it. Life’s not a straight path.

One thing I truly fucking dislike about the development life is knowing about server administration. I think that the mental hurdle that is to develop a huge application, make a stable dev environment, learn all the tools, tricks, techniques, modern standards, processes whatever, detailing software engineering are way tf too much to also handle server admin shit.

We don't have anyone at work that deals with that, and as such my devs need to know how to do entire series of maintenance shit that just takes time and effort plus hours of notetaking and study. I mean I get it, they should know their way around a linux environment enough to troubleshoot issues that are related to the os when working with some tools, but fuuuuuuuck me man, setting up a server, even for the holy grail of easy (standard lamp stack) takes way tf too much.

Wish we could have a dedicated server admin in the team.

I know where my faults are, setting up servers is something that I know but just can't be assed with in terms of keeping up, I wish we had a devops dedicated server admin deployment guru cuz I really cannot stand losing hours doing this shit.

It also diminishes good s admins in value, "weLl ThE deVs caN do It" YEAH BITCH but wouldn't it be nice to have an expert concentrating on JUST THAT?

FUCK man

Trying to troubleshoot this busted ass code for a client. Meanwhile, my wife is in class and my two daughters are blowing chunks.

Staring at devRant isn't fixing anything either. Lol

Decided to something productive.
PSU (smps) died 😡😡.
Now I got to troubleshoot that first

A conversation that i had with my co-worker today. I was having trouble getting into UAT to troubleshoot.

me
i lost access to UAT again

co-worker
F. So secure we can't even get in

me:
lol

co-worker:
I'll email whoever we did last

me:
i can get through the first phase(where you enter pin+rsa)
it denies me access after that
says bad username or password

co-worker:
Oh ok. Prolly just need to reset your pwd then. I'll find the email for helpdesk and fwd.
At least ur RSA works.

me:
yeah what a joy

co-worker:
If it's locked you may need to try from a Windows box. Horizon is bugged on Mac where the submit button stays disabled even when you type a pwd.

me:
i couldnt contain my happiness that my RSA worked
😃

co-worker:
Yeah it's exhilarating
Whenever I pick up my rsa token my life re-finds it's purpose and I feel like I'm meddling through a field of sunflowers.

I once tried to get my RSA token tattooed but it switched too quick.

me:
lol its faster that Usain Bolt

co worker:
Russia got kicked out because of their RSA tokens

Argh fuck you Microsoft for blocking my precious mail server. I can't believe that you were the only one. Even google accepts my mails with every fucking test passed...

Oh and not to mention that in the no delivery report you are referring an error code which is not present on the linked troubleshoot page. Thank you once more, you piece of shit.

Should have listened to the articles about why I don't want an own mail server...

God I hate React so bad
I get the hype but omg it is so confusing
Literally everytime I try adding something nothing works and I have to troubleshoot, EVERYTHING is a problem
And don't even get me started on REACT + TYPESCRIPT

IMO VueJS is just a smoother nicer experience overall

Spent hours synthesizing few novel ideas on Notepad, and then did Ctrl-A, Ctrl-X so I could just paste it in my private blog. The blog wouldn't respond, ssh'd into the server to troubleshoot, and then realized my habitual use of Ctrl-C destroyed that very content I spent hours on. Only realized this after I got the blog back up running again. X-( I should start getting into habit of using VSCode or Gvim more.

Is it OK to punch a game dev who codes stupid numeric bugs?

So my wife got into Stardew Valley, that admittedly awesome comfort game farming simulator.
She went pretty far in the game, and found some item that was supposed to highly increase the damage she could inflict onto cute little monster thingies.
It didn't work as intended.
Since equipping the piece of shit all her hits did 0 damage. She tossed the item away but the problem persisted. And on and on...
She took to the googles to try and find some explanation, and apparently that is a fairly common bug for mobile devs.
Then she called in the big guns (that is how I'm calling myself in this case, you will see why).

Apparently there is some buggy piece of shitcode somewhere in the game with a numerical insecure routine that overflows the attack modifier. I.e. if it was supposed to increase from 1.990 to 2.010, it actually went all the way down to -0.4.
She was lucky her attacks weren't increasing the monsters' HP.

We found a forum post where some dude said that he managed to edit the game save file and reset the negative-value attack increase modifier variable. Seems easy enough at first, but my wife uses iOS. Nothing is ever so straightforward with apple stuff.

We did get to the save file, she emailed it to me (the file has no extension and no line breaks in it, so we facepalm'd on a couple attempts at editing it directly).
I finally manage to get it into my personal 11-yo laptop... that won't open a single line file that big.

Cue the python terminal. Easy enough to read the file into a string var and search for the buggy XML tag. Edit the value and overwrite into a new file. Send it back to her by email. Figure out how to overwrite the file in iOS.

Some tense moments while the game reloads... and it works!!!! Got some serious hubby goodwill points here.
Srsly, this troubleshoot process is not for technophobes. It is out of reach to pretty much every non-techy user.

And now back to the original question: If I ever manage to find the kid who coded a game-breaking numerically unsafe routine and shipped it as if every test in the planet had waved it bye-bye, can I punch them? Or maybe buy them a beer, let's see how I get to cash that hubby goodwill tonight :)

Dependency hell is the largest problem in Linux.

On Windows, I just download an executeable (.exe) file, and it just works like a charm! But Linux sometimes needs me to install dependencies.

At one point, I nearly broke my operating system while trying to solve dependencies. I noticed that some existing applications refused to start due to some GLIBC error gore. I thought to myself "that thing ain't gonna boot the next time", so I had to restore the /usr/lib/x86_64-linux-gnu/ folder from a backup.

And then there is a new level of lunacy called "conflicting dependencies". I never had such an error on Windows. But when I wanted to try out both vsftpd and proFTPd on Linux, I get this error, whereas on Windows, I simply download an .exe file and it WORKS! Even on Android OS, I simply install an APK file of Amaze File Manager or Primitive FTPd or both and it WORKS! Both in under a minute. But on Linux, I get this crap. Sure, Linux has many benefits, but if one can't simply install a program without encountering cryptic errors that take half a day to troubleshoot and could cause new whack-a-mole-style errors, Linux's poor market share is no surprise.

Someone asked "Why not create portable applications" on Unix/Linux StackExchange. Portable applications can not just be copied on flash drives and to other computers, but allow easily installing multiple versions on a system. A web developer might do so to test compatibility with older browsers. Here is an answer to that question:

> The major argument [for shared libraries] is security, that if there is a vulnerability in a commonly-used library, then only that library has to be updated […] you don't have to have 4 different versions of a library installed

I just want my software to work! Period. I don't mind having multiple versions of libraries, I simply want it to WORK! To hell with "good reasons" for why it doesn't, and then being surprised why Linux has a poor market share. Want to boost Linux market share? SOLVE THIS DAMN ISSUE!.

Understand that the average computer user wants stuff to work out of the box, like it does in Windows.

When I hit the endpoint from Postman it works. When I hit the endpoint from my application that pushes data to the endpoint it doesn't work, returning a 404 status code. I KNOW the endpoint is there and operational and that both Postman and my application have the same endpoint configured, letter for letter.

So lost. So confused. What the hell is going on.

I decide to install Fiddler to monitor the traffic to see if I can see anything helpful.

I initiate the request again from the application and immediately see that the request size is huge. BAM. It immediately hits me, the payload to the endpoint is too big and the server is "rejecting" it with a 404. I post a smaller request with the application and it works fine.

Yay, saved by Fiddler.

Why does the endpoint default to 404 in such scenarios. The definition of 404: "the client was able to communicate with a given server, but the server could not find what was requested"

In my case, the 404 returned was a red herring. I understand that the substatus code gives more information on why the 404 was returned, in my case the request size being too big, but 404 in general feels like the wrong status code to return because the endpoint IS there. It made me troubleshoot the wrong thing.

Thanks, IIS.

This is the reason I will never be with IT: I recently got hired as an IT assistant at my college. I was in charge of solving issues in an entire building actually. I was so excited to be able to go around to resolve and troubleshoot problems with people's computers. The responsibility and pay were good, but the fact that people had next to no problems, but I had to be in the same room with students during virtual tests and lessons just in case. I had to stand in the same spot for 2.5 hours watching people take a test. Whenever they DID have a problem, they just had to refresh the page! People gotta learn that I don't have to be in the room in order for people to decide basic troubleshooting. Extremely boring and tiring. No challenges and barely any problem-solving. This is why I'm on Devrant and not Fixrant.

1. Update some packages
2. Linux machine stops working soon after
3. Panic
4. Go get windows machine to help me troubleshoot the issue
5. Starts windows update on startup
6. Panic some more

I'm noticing that installing a new distro and making it your main distro tends to be very stressful to me.

Here's a couple of reasons why:

There's this anxiety I get that is just crazy, like I need to set this thing up perfectly, meanwhile I have work to do.
And the thing you estimated to take 2 hours at most ends up being a full week.
Work starts to pile up but can't just shake the obsession with setting this thing up.

Another reason is that usually my main distro instance tends to be VERY customized.
So much that when you switch, you need to configure those things again, and troubleshoot a lot.

Troubleshooting isn't a problem in itself. The problem is that you're trying to troubleshoot with a machine that needs troubleshooting.

the shell, the editor, the terminal, the window manager, tmux, the notifications, the custom kb layout. it was all so neatly customized that fixing problems on the machine was manageable.

but without all that I feel like an idiot.

Even something as simple as keeping having youtube music to focus is now intermittent because you need to restart the X server.

Maybe my problem is that I don't do well for bootstrapping.

Anyhow, I'm really stressed right now, but I think it'll be worth it.

when this God for saken error is taking forever to troubleshoot and I'm getting hungry...

Tales from University Tech Support:

Me: please send us 2 or 3 times you're available for us to troubleshoot that issue
Them: I'm available at 3:30

Obviously not a Math Major...

Some people are good at troubleshooting, some people are just good in asking other people to troubleshoot it for them. Which one would you rather be?

*le me being frustrated af trying to compile asm.
.section won't work for fasm. And some other things won't work for Nasm.
Now I got the .obj aka .o from the .asm. But ldrdf.exe from the nasm compiler isn't working properly. And I can't find a troubleshoot online. Seems like this will be a sleepless night...

I was assigned a task to troubleshoot some buggy code. I am a developer and I don’t know how to get started. Does anyone else experience this kind of anxiety? Where you’re asked to apply your skills and suddenly your brain just shuts down and you feel like you know exactly nothing? I’m older than most coders in my field. Onset of some kind of brain disorder?

Need advice.

So the class I TA is learning how to use heroku for website testing. It is going up on fire because of a shit tonne of errors everywhere. The professor is adamant heroku is what is used nowadays for testing (over using FTP) so we will have to help 200+ people troubleshoot without knowing much ourselves.

My question is what are some other modern website testing mechanisms? Preferably some that have retard proofing in them.

I work for a particular tech company doing chat based support where I troubleshoot a certain email application.

And one of the most common phrases I get is: "Hey Mister IT Guy, I am suddenly missing all of my contacts and Calendars. This super sucks! I had to rebuild my email profile to make my email work again!".

I really wish when they teach computer literacy in school they drilled "Learn How To Back Up Your Junk" more so when stuff like this happens I can get them back up and running in 10 minutes instead of telling the user they are going to have spend hours rebuilding their calendar and contacts.

I learned very quickly that magic globals are baaaaad.

I mean, it's easier than using a queue for passing data between threads, right?

These goddamn fuckers who every week spam people because their CI or code is broken. Apparently it's more important than other projects. Douchenuggets send an email and CCs the whole department and all the bosses and basically says "It's all broken, the whole company needs to work on this asap, it's possibly x other person's fault".

Then when you try to troubleshoot it because bosses want it fixed, the dumb pieces of fuck made a bug in their code that they could have easily fixed if they took the time to troubleshoot themselves instead of panicking like jackasses. Or better, have good tests and actual error handling.

I swear some day I am gonna get into a fistfight I started because of this bullshit.

Previously, I've shared a story about the internship at an IT department for a local "center for student guidance". This was back when I was in high school.

Since nearly everyone was incompetent with tech, we often got a call for dumb IT errors. We got a call that a user had a black screen and could not work anymore with her computer.

So we went to troubleshoot, she was correct... A black screen but her computer was still booted. So we moved the mouse and the mouse showed up. We pressed escape and she could continue...

She called the IT department because she was on the last dia of her powerpoint and the text for "press escape to close the dia presentation" has disappeared. She never touched her keyboard or tried anything :D

Got bored and decided to try and compile X11 Quake (WinQuake) so far trying to troubleshoot some undefined references

A file that I had copied from the company network drive into my own. VS Code to edit the content according to a tutorial provided. IDE doesn't work with the given file, dependencies not resolvable, so let's troubleshoot. Open the file in question inside the IDE, the file contents are those from the tutorial?? Turns out I didn't edit the file on my own system but on the network drive. At least it wasn't a critical file. 🤦

Watched 2 different vendors struggle to get something going.

I stayed quiet during both meetings, the first, was a misconfiguration error on their project code. They were tailoring the product that they sold my institution, I could see the simple error: key-value settings on one of their json files (it is a dotneto app)
I don't get paid to troubleshoot the code for an external company, so I was silent, knowing full well this would take longer to get done, needless to say, I had originally advised against purchasing this product but was not listened to, very well then.

The other was a configuration issue on the side of a different Java based product, there were some strange XML configuration entries, some other project files that made little sense, but again: quiet.

Department head is concerned about the delays that this might cause and will still not ask if I am willing to help since he knows I A) was against this product purchase from the get go and B) knows DAMN well I will say that I don't get paid to troubleshoot the issues that third party vendors charging us over 100k of product "worth", they wanna spend the money on "enterprise" shit that does not work,they can deal with their own shit programs.

Morale of the story: money moves people. If there is no bling in my account: then I ain't doing it.

Now, I do get paid well for what I do, and for that I do bust my ass, for everything else: there is mastercard.

Learning to troubleshoot issues with vms. Had to break a vm with a script I was given and then fix it. Docs I was given said x error should be in y log. I check the log; nope. Check the other logs for other possible errors mentioned; nope. Turns out something else broke instead and before of the thing I was supposed to break. Rip me

In my first few months of my first dev job, I written this fragile piece of code in, trigger warning, PHP that sent out email reports to my clients. It was a two men team, and we have no clue about TDD or how to do unit testing for such code. We would just run that piece of code manually do send out dummy emails to ensure things were working.

One day the code broke. I was told by my boss to fix it. Spent the entire day trying to fix but couldn't get anything done. Finally at around 7pm my boss came by and asked why is it I couldn't get it fixed. He helped me troubleshoot and fixed it. And subsequently told me "c'mon man you're better than this."

It turns out that he changed a part of a code that was supposed return an array of strings to an array of objects, adding a second attribute that wasn't even in use.

So what that meant is that he changed a piece of working code, to include a property he didn't need, committed and push to production without even manually testing it. AND TALKED SHIT TO ME.

That was the day I learned git blame and began my journey on TDD.

Triaging this project that's running on IIS makes me feel like my skillset is wasted on such banal garbage - while at the same time hoping nobody realizes what a mistake it was to put me on it because I have no idea how to troubleshoot or fix it.

I try not to be that guy who blames every issue on their tools but I can't believe some of these issues and respective fixes. Our QA was down for 2 months because I hadn't uninstalled a default module which prevents POST requests.

This morning at 5:30 AM I was awoken to 20 text alerts for services being down.
Seems they had been down since 2 AM but the previous shift didn't take action.

Long story short:
An outsourced common component is unavailable, and the team responsible doesn't know how to troubleshoot.
I pointed them to the exact issue.
We are now 10 hours into the outage and they still don't know what to do.

Had so much fun doing crowd-programming to troubleshoot an issue at work yesterday! Because, you know, three is a crowd. ;-)

I know that when a deadline is present, things like cyclomatic complexity might be something that is a left aside. But I hate so much having to troubleshoot a method with 15 levels deep of nested if, try-catch, loops... Fuck!

How was I able to fix this bullshit report generator task?

Simple bitch. I am that fucking good. Matter of fact. I am more than good. Sit the fuck down and listen.

That fucktard you have over there acting as a faculty member teaching kids about code and security? Blame that bitch for the horrible code that was NOT working since he wrote that with absolute disdain for software engineering and without taste or finesse.
Yeah I was able to troubleshoot his monster of an app. His ass is the reason why people hate php, giving the lang and community a bad name and shit.

Pleased to meet you btw.

I am Alex. Your new rockstar.

To my manager: i got it babe don't worry. I'll be your huckleberry.

I am out.

I love it when someone wants you to troubleshoot an issue but will not give you a test user account to test with. So you have to sit with a user or talk with them over the phone while you troubleshoot. I'm literally elbows deep in the code and database, but you won't give me an account for security reasons. Ok, that makes complete sense.

I'm currently migrating one of the companies services from technology A to an B based solution...
Today I had to remotly troubleshoot an error occuring somewhere on our client's backend application, that wans't enabling us to register any given webhook to our endpoints...
We finally gave in and looked up the data packets using a sniffer only to find that the only difference was that in the A technology project our staff ended up returning a Status Code plus the respective Reason Phrase, in our newest version we only send the HTTP Status Code... Guess who wasn't aware of HTTP 1.1 RFC consideres the Reason Phrase optional and an unecessary overhead??? God dammit... In simple terms...

I have come to learn that when you script nearly everything in your job, what remains are the real pain in the ass clients.

I have told this particular client before that the issue does not lie with our equipment. I have verified while on a conference call with the other vendors that I am out of the equation. They concurred while the client was on the phone.

And yet.... Today, almost two weeks later, I have been assigned a ticket to re-verify our settings and to potentially troubleshoot !OurEquipment.

What hurts me the most is that my CEO is the best boss I have ever had, but he panders to these clients that do not listen to the diagnosis.

I am literally doing the same thing over again. I am not expecting a different outcome. I don't know why others expect a different outcome.

Because of this one example (and other similar ones), I am so tempted to leave an otherwise great company and environment.

Spending six hours installing Antergos and reinstalling Antergos because I can not log into my laptop when I install i3 nor when I install GNOME...

Turns out the drivers for NVIDIA got installed (I checked it without thinking about it) everytime and that was the culprit...

Lesson learned: install everything by yourself, that way you know what you have on your laptop, and makes it much easier to troubleshoot..

Please.....

Don't troubleshoot over my shoulder.
Don't point at the screen over my shoulder.
Don't suggest the troubleshooting step I'm currently on, while pointing at the screen and whispering over my shoulder.
Don't think out loud as you are troubleshooting over my shoulder.

Please....

I tried to post a comment to someone's post and without UI feedback I get the API response in the HTTP request: "Comment not valid". This isn't enough information for me to troubleshoot what is a valid comment.

So my (windows 10) laptop decided to suddenly forget about its Bluetooth capability. And about its Bluetooth hardware.

Now, I did not restart my system, I just left it idle for a while. Heck, I played rainbow six before leaving it idle (with a Bluetooth mouse, of course)

Tried checking for the settings (didn't find any settings related to Bluetooth service), didn't find it in device manager, useful the troubleshooter (bastard says the problem is I have no Bluetooth hardware installed), tried restarting the system, checked in bios menu (couldn't see hardware info printed in bios system info), tried updating/reinstalling the driver.

The hell am I supposed to do?

I've just learned that our front-end application throws a simple 404 error when trying to retrieve an avatar that does not exists.

But our technicians/support use this error in the console to show the customers that there is indeed a problem with the application functionality but have unsufficient logging from the back-end to troubleshoot with their internal tools.

What a bunch of liars trying to keep the customer satisfied and it works relatively well :D

Found another gem in the code-base I've been given to troubleshoot.

Let's call recv(), get the TLS encrypted message, and then call BIO_write() and SSL_read() instead of offloading it to OpenSSL.

I had to contact technical support for an API. I’m pretty sure I was emailing with a bot because I was getting all sorts of stupid replies.

Me: I’m using your SDK for language X. It’s returned null for some properties. In the user portal, I can see there are values for those properties for the transaction. I don’t know why I’m not receiving them on my end.

Tech Support: Hi! I see the following was sent in the API response. [Sends api response to me.] You can also go the the portal to see those values.

Me: Yeah, I know. You just repeated everything I wrote to you. I don’t want to go to the portal. I told you I want to figure out why your SDK doesn’t seem to map those properties correctly when I receive the api response.

TS: Let me look at the docs. I think you need to send the properties you want in your request in order to get them back in the reply from the api. Such as <property>value<property> in the xml message.

🤨 The docs do not say that. They don’t even imply that.

Me: What the fuck?! That makes absolutely no sense. We have already established that the api **is** returning values for those properties. I want to troubleshoot why your SDK is mapping them as NULL.

Is it normal for a developer to go the customers to troubleshoot a certain problem?

I mean, we got technicians & support department

Goodbye Ampps, hello Valet!!

Just got a Macbook Pro recently for personal web dev stuff. Previously, I usually use Ampps (like MAMP) for my local development.

But I want to move away from that as I wanted to go through the whole process of setting up my own local dev env.

After 3 days of trial and errors and many deadends, finally managed to get an existing Craft project running on Valet. The most tedious part was figuring out how connect Sequel Pro to local MySQL.

Through this whole process I've learned how to use Homebrew, setup MySQL with Sequel Pro, use Valet and most importantly, learning how to troubleshoot these problems...

Exclaimed a big YES! And mum came rushing into my room thinking I was mad... whateva...

Next step, figure out Docker.

#feellikeimoncloudnine

Production issue happens, to get into server to investigate - first write a brief description of the issue, get management approval, then find 2 administrators who each holds half the password to the server, web conference them to key in password on a remote utility, finally, log in to troubleshoot.

It is a problem to troubleshoot a problem.

Node isn't setup correctly after installation. 😤😩

Help me troubleshoot this issue so that I can move forward in my lesson please!

I just wanna learn dammit.

That feeling when you are on call and a report comes in of a feature not working correctly for a system you know nothing about. Sure, I’ll dig in a bit and troubleshoot before throwing over the fence. Hmm, feature was never coded - not in a shelve-set or branch…just never done. Was supposed to be done over a year ago I’m told. Humanity is too sick to survive.

Had to install .net 1.1 to try and get some shitty old db application to work. Still doesn't work, but it messed up all my wcf services. Fml. >_<

'Tech debt' is the word that every CEO hates to hear during roadmap review.

Instead, talk about how certain part of the code will drastically slow down future development, make it more difficult to troubleshoot, and reduce engineering happiness overall.

Scarily relatable

Surface Pro shows battery status at 0% - Not Charging. Turns off as soon as power is removed. Looks like battery is dead. Anybody have any troubleshooting tips?

In case of hot debates...

Spent the day helping someone troubleshoot why they can't print from their Samsung tablet, because somehow as a DBA I "know how to do that stuff." Never figured out why it wasn't working.

Best way to troubleshoot a long ttfb on a wp woocommerce site? Yes I know wp and woo == boo. Still, a friend of mine has a shop and needs some help with it. Shared hosting, 6-7sec load for homepage, 4-5secs for product page

1) After many years of development the thing that grew the most is my capability to troubleshoot much more easily most issues, both physical or virtual, with greater enjoyment from such accomplishments.

2) The power to create something from nothing is a great feeling, especially if you keep on personal projects and most of your dev passion you keep it outside the working environment.

3) Career paths can easily be opened in case you live development as an infinite cycle of adaptation and improvement.

Buy Verified Cash App Account: Navigating the Digital Transaction Landscape
In an age dominated by digital transactions, the concept of purchasing a verified Cash App account has gained significant traction. This article aims to explore the nuances of buying a verified Cash App account, elucidating the advantages, potential risks, and offering a comprehensive guide for individuals considering this financial move.

Introduction
The Growing Trend of Buying Verified Cash App Accounts
As online transactions become more prevalent, the trend of purchasing verified Cash App accounts is on the rise. Users are increasingly recognizing the added benefits and security that come with having a verified account.

Understanding the Importance of Account Verification
Account verification is a crucial step in enhancing the security of digital transactions. A verified Cash App account provides users with an additional layer of protection, making their financial interactions more secure and reliable.

Advantages of Purchasing a Verified Cash App Account
Enhanced Security Features
One of the primary advantages of a verified Cash App account is the incorporation of advanced security features. These may include multi-factor authentication and additional verification steps, adding an extra layer of defense against unauthorized access.

Increased Transaction Limits
Verified accounts often come with substantially increased transaction limits. This proves beneficial for users engaged in larger financial transactions or those running businesses through the Cash App platform.

Access to Exclusive Cash App Features
Apart from heightened security and increased transaction limits, verified accounts may unlock exclusive features within the Cash App. This could range from priority customer support to early access to new features and promotions.

How to Safely Purchase a Verified Cash App Account
Researching Reputable Sellers
Before entering the purchasing process, it's crucial to research and identify reputable sellers. Reading reviews and testimonials can provide valuable insights into the credibility and reliability of a seller.

Authenticating Account Legitimacy
Ensuring the authenticity of the accounts offered by sellers is paramount. A legitimate verified account should have gone through the necessary verification steps outlined by Cash App.

Ensuring Transparency in Transactions
Transparency in transactions is vital. Buyers should choose sellers who provide clear information about the accounts, including their verification status and any associated features.

Risks and Precautions in Buying Verified Accounts
Common Scams in the Verified Account Market
The digital landscape is not without risks, and the market for verified Cash App accounts is no exception. Being aware of common scams, such as fake listings and phishing attempts, is essential.

Tips for a Secure Transaction Process
To mitigate the risk of falling victim to fraudulent transactions, following best practices such as using secure payment methods and verifying the seller's credentials is crucial.

Step-by-Step Guide to Verifying a Cash App Account
Understanding the Cash App Verification Process
Before attempting to verify a Cash App account, it is essential to understand the process thoroughly. Familiarizing oneself with the required documentation and steps ensures a smooth verification experience.

Submitting Required Information
During the verification process, users typically need to provide personal information, such as a valid ID and proof of address. Ensuring the accuracy and legitimacy of this information is key to a successful verification.

Navigating Potential Challenges
While the verification process is generally straightforward, users may encounter challenges. Being prepared to troubleshoot and address potential issues ensures a seamless verification experience.

Conclusion
Summarizing the Benefits and Risks
In conclusion, opting for a verified Cash App account offers users enhanced security, increased transaction limits, and exclusive access to platform features. While potential risks exist, informed decision-making and adherence to safety precautions can lead to a positive experience.

Encouraging Informed Decision-Making
As users consider the option of purchasing a verified Cash App account, it is crucial to approach the process with caution and awareness. Choosing sellers with proven credibility, staying informed about potential risks, and following best practices contribute to a secure and positive experience.

Firstly, I'm not a dev, and I don't play one on telly. But I would like to say that I am qualified to tell those gits at Microsoft that I'm just this side of seriously laughing myself into the Moscow Suburban Branch of Are You Fucking Kidding Me With a Pages-Long instruction tutorial that even Jesus Christ would read it and tell the Microsoft writers to go fuck themselves, and he would put a word in with his Father to personally keep these wankers VERY FAR out of Heaven.
I'm specifically referring to the sound on my laptop being fucking lame. And I don't wish to attempt to add up the time I've taken to read and then attempt to implement the procedures, only to find they were complete bullocks. These were supplied on the microsoft answers website.
I click on a playlist. It sounds heavenly. I stop the playlist and put a pair of headphones on and insert the doo-dad Koss sent to me gratis as an adapter. Silence. Click on 'troubleshoot sound problems.' Sounds emanate from the headphone!. Repeat. This is throwing my toys out of the pram, I admit it.

ghub piece of shit

damn fucking shitty software. It happened to me in the past(like thrice times) that my mouse got randomly locked at the highest dpi until I uninstalled and reinstalled ghub... well it improved with the time and lately I haven't had that issue anymore, but hey today just for my daily stand up the mic decided to stop working out of the blue(headset is logitech too)... then fuck it didn't have time to troubleshoot that, made my way around using camera mic 🤪

Soon after I finished my meeting, decided to check on ghub to see if the software didn't detect the headset or whatnot... as soon as I tried to open it "ghub is updating", because of course, it can't tell you in any way that you should update it or your devices would not work until you open the goddamned software

I've got a dev server where I run some test sites in WP using EasyEngine, because I want to get accustomed to WP in Docker.

It asked me to update, and I was like "sure". Now whenever I want to setup a website I get "easyengine couldn't create username"

I figured ok I'll use WordOps, which requires migrating from EasyEngine to it. I was like sure, and next thing I know the "migrated" websites that it was supposed to properly migrate automatically are down, and I can't get an SSL issues for my new site.

All threads on both issues don't help.

It was supposed to be a 5 minute job and it turned into 3 hours trying to troubleshoot. Now I'll spin up a DigitalOcean server and install a quick WP site.

Fuck both EasyEngine and WordOps <3

I thought EasyEngine would be cool but seeing the very limited community activity it's not worth the risk even having it in a dev environment.