I just spent 5 minutes trying to fix an error saying that I am missing a ";".

I saw a ; at the end of statement but I kept on getting the error.

After cleaning the monitor the ; disappeared and I was able to see the problem.

Clean your monitor once in a while.

When you implement a 3rd party payment system, and it doesn't work... and their support can't fix the problem... So you debug their code and send them the revised code and they update their GIT repo and update their documenting.

-- How I feel at work lately, in terms my wife understands --

Me: There's a gas leak, we need to fix it.

Manager: Yeah, use some duct tape, here's a roll.

Me: That's not how we fix a problem like this.

Manager: Will it work to solve the problem?

Me: Only temporarily

Manager: Ask your co-worker if you need help using duct tape, he's used it before. When will it be fixed?

Fucking someone has to fix the recruiting process.

Fucking who gives a shit about your experience, and what you did so long.

Here take this fucking shitty problem that I googled, so that I can judge you by this one fucking problem.

Oh, youve worked on variety of technologies? Fuck you.

Fuck these interviews. Fml.

Got an email from client with subject starting with "VERY URGENT", the email mentioned how urgent it is to fix this issue multiple times, it implied that they couldn't do anything else while this issue existed, but they were very light on details. So sparse on them that I couldn't reproduce the issue. 15 minutes after the original email I write a reply asking for some clarifications.

They proceed not to reply for 4 days. Fix took 5 minutes after they explained the problem better.

Apparently it wasn't so urgent after all.

My dad: Hey Sébastien, I think my computer has a problem, can you look my computer ?
Me: Sure.
*walks in front of the computer*
*looks at the screen*
*go away*
My dad: But, you don't fix it ?
Me: Nope, you just asked me to 'see' your computer
*walks away*

Client: Please fix the logo.
Me: Okay, what needs to be fixed exactly?
Client: Put this word next to that word(shows me an example).
Me: Okay, no problem.
*after 5 minutes*
Client: You did not do what I asked for. Please fix the logo. Make it look better. Make it bigger and more outstanding. Dont change my logo
Me: Okay, I will revert the changes.
*Reverts to the old logo, and only does that as I do not fucking know what to do with oudstanding for fucks sake*
Client: I will talk to your boss. No one cares. My web site is not even finished and no one cares.
*It is finished, now the client looks for small things to make a big issue of*
Me: Could you please tell me in detail, what do you need to be fixes?
Client: I want the wording better. Im going to talk to your boss...

well fuuuck fucking fuck Im pissing blood!!!!!!!!!

User: oh! An error message.

Message : Problem XY has occurred. Do YX to fix the problem.

User: Ok I try everything except what it says. ...
Ok that didn't work. I ask the IT

IT: Have you tried what it says?

User: no I didn't know ...

IT:ok do it.

User: 0.o It worked! why do we pay you if it is so easy?

Every goddamn time 🤦🏻‍♂️

I am a programmer, and if you ask me to fix your pc, I accept the challenge... After all, I can Google a problem and implement a solution like no other, you are right to have come to me.

Got assigned to fix a bug in a validation function that would always return true even if the data is invalid.

I looked at the code from the function and noticed that the only line of code in the function was "return true;"

Apparently, the programmer who wrote this function a few years ago got fired and no one ever finished his work.

Now it amazes me that no one ever has looked at the problem and just assumed it would be a complicated bug.

One of our clients deploy their own server app. So this happened after a prod deployment. (4am)

*Cellphone rings while sleeping*

Client : we need you on the conference call now. URGENT!

*Gets on conference call*
*Client explain the problem*
*Explaining to the client that the problem is in their side (https connection not working, either network or certificate problem)*
*Client doesn't believe it and pushes me for a fix that I have no control on*
*4 hours later in a heated conversation*

Client : ok problem is on our side. We used our SSL certificate from staging with production and thought it would work.

Me :

Aaaah...I just got back from a meeting because of a production data problem caused by an analyst who keeps making mistakes that screw up client data. I wrote a program to automate most of it and everybody initially accused me of having a buggy program, only to find out she wasn't using it, never did.

"Why aren't you using the program then?" was asked. "Oh, well, I just understand my way better," she replies, "When I make a mistake at least I understand why."

Pause....

"Then, um, if you know you're making a mistake, why don't you fix it?"
"Because my process is so manual and labor intensive sometimes it's not worth it to go back and fix it, because I'd have to do everything over again, and you guys are much better at fixing this stuff than I am."

I indicated that everyone is too busy to stop and fix her mistakes, to which she then asks:

"So if you can't fix my mistakes, what am I supposed to do?"

A real interaction I just had...

Team Member: "Can you handle this ticket for a bug fix?"

Me: "Whats the problem?"

TM: "We aren't exactly sure..."

Me: "Ok, so can you show it to me?"

TM: "We can't get it to happen again, and when it does the machine freezes and we can't debug it..."

Me: "So, if I find a fix then how do we test to make sure it worked?"

TM: "I'm not sure..."

Then today,

Product Manager: "How's that bug fix going?"

Me: "Well, let's see. The problem still hasn't been defined. I have never been able to recreate the issue. I have a hacky fix in a PR..."

PM: "Great, so we can deploy today?!?"

Me: "No, because we have no way to reproduce or test this issue at all..."

PM: "Do you think your fix will work?"

Me: "Honestly, no. If you're asking for my opinion then you can have it. IMO this is NOT a bug fix but a change to how the system operates altogether. This system was built by someone who didn't know what they are doing. We have done our best with it but it is a house of cards. And now the solution is to replace a card at the bottom layer. It is likely that no matter what fix we do (even when we can fucking test it) that it will topple the house of cards..."

PM: ~Looking at me in disbelief~

Me: "If you ask me for my honest professional opinion then you will get it. Keep that in the future if that honest response was outside what you expected."

PM: "I will do that, thanks for your assessment"

Where do we go from here? God only knows.

Praise Joe Pesci

Woke up early. Feel great. Even office coffee tastes great. Today is going to be a good day.

Lead QA: - Hey I'm fixing some stuff in production, and now I can't reach it. Do you have the same problem?

TODAY IS A GOOD DAY, GO FIX YOUR OWN PROBLEM CUNT.

COFFEE TASTES FUCKING GREAT.

Dammit, I can't even describe how much I hate when I'm researching to fix a problem, find a forum/question and the guy answering it makes a post saying "Forget about it, solved it" but doesn't say how.

Roommate's boyfriend visits just to work because his laptop can't connect via WiFi anymore.

Described the problem and fix attempts yesterday, he got two other tech savvy people involved, now suspects hardware problem.

I needed <1m to re-activate the WiFi adapter, now I'm seen as the local tech God as I deserve.

Asking a question on Stackoverflow, explained as best as I can, provided links code everything.

5 minutes later I see a notification. Wooooo someone will help me fix my problem.

Some Indian dude suggested an edit.

You know what his edit was?
...
CAPITALIZING THE FUCKING LINKS

Actual email I just sent to a customer:

"I logged into your account and I see the problem. I will update you and have it fixed either by tonight or tomorrow morning. It is a rare bug we have encountered before, and we are working on it as you read this. "

The truth:

"Im fucking drunk right now. I know that error. I put off fixing it for awhile now hoping it wouldn't come up because it's fucking annoying to fix. I'll try to fix it tomorrow morning, k no promises though. If I can't I'll still have your problem taken cats of it just means I'll have to do it manually. Anyway.. Gonna drink some more now, bye. "

P. S. There is no we. It's just me. K bye.

Girlfriend (she has little idea of tech) was asking if I could fix her notebooks wifi.

I didn't answer that for a week.

Yesterday she really needed wifi, so she went to google and followed several posts - until she managed find the problem and to reinstall her wifi driver for the first time! She was so proud of herself.

I hope I'll never forget that grin of her - full of triumph!

I couldn't be more proud of her myself

The problem with Linux... It's stable, you can get exactly the desktop experience you want out of it, BUUUUT, there's always an urge to tinker a little more, then you break everything and it takes hours to fix

Okay so about a year ago these FUKKING IDIOTS decides, against my recommendation, to do this quick-ugly-hack and ninja it into production.
I tell them its a FUCKING BAD idea that will blow up in a year or so...
But no, just go go go!!!!!!!

Now a year later, shit blew up badly. A total FUCKING derail. These new idiots asks me to "fix the problem", the same fucking problem I predicted and warned them about a year ago. So now i have to clean up their ducking mess because "Nobody else knows how to fix it".
What the FUCKING HELL do we pay them fuckkkers to do?!!

New idiots you ask? Yep, because 3 out of the 4 original fucktards already left the place in order to go and make some other new collegues lives fucking miserable.

FUCK YOU FUCKING MOOTHERFUUUKKKEEERRRRRSSSSSS!!!!!!!!!!!!!!

When the junior insists that it's fine setting server permissions to 777

when u spend 2 hours desperately trying to fix a bug. Give up, off the computer and get ready for bed. the moment you get comfortable and ready to sleep. You solve the problem mentally in ur head. Get back up, on the computer and continue coding.

Annual performance peer review

Person who did review me wrote in the section “skills needed to improve”:

“He is introverted...”

Bloody hell!! What a big problem :) and how in earth you can “fix” it? And why everyone expected to be extraverted??

Customer calls since they got problem x
C: Hey its xyz we got a problem
Me: hey what's it About?
C: <explains problem pretty poorly>
Me: uuuuuh.. I've written it down and look to fix it as soon as possible
C: why? Just TURN OFF the problem

No. This is not how it works. This is not how any of this works.

My laptop had a full meltdown and wouldn't turn on. It tried to start up then the screen went blank. It's happened before so I lost hope pretty quick.

Just spent the whole evening trying to fix it reinstalling windows and now I spot the problem. The HDMI is plugged in to a monitor that was off. My laptop was fine the whole time. Fml

"Why is this not working, it was working before!!??😤"
--finally fix problem--
"How the hell was it working before??"

Application has had a suspected memory leak for years. Tech team got developers THE EXACT CODE that caused it. Few months of testing go by, telling us they're resolving their memory leak problem (finally).

Today: yeah, we still need restarts because we don't know if this new deployment will fix our memory leak, we don't know what the problem is.

WHAT THE FUCK WERE YOU DOING IN THE LOWER REGIONS FOR THREE FUCKING MONTHS?!?!?! HAVING A FUCKING ORGY???????????????

My friends took the time to find your damn problem for you AND YOU'RE GOING TO TELL ME YOU DON'T KNOW WHAT THE PROBLEM IS???

It was in lower regions for 3 MONTHS and you don't know how it's impacting memory usage?!?!?! DO YOU WANT TO STILL HAVE A JOB? BECAUSE IF NOT, I CAN TAKE CARE OF THAT FOR YOU. YOU DON'T DESERVE YOUR FUCKING JOB IF YOU CAN'T FUCKING FIX THIS.

Every time your app crashes, even though I don't need to get your highest level boss on anymore for approval to restart your server, I'M GOING TO FUCKING CALL HIM AND MAKE HIM SEE THAT YOU'RE A FUCKING IDIOT. Eventually, he'll get so annoyed with me, your shit will be fixed. AND I WON'T HAVE TO DEAL WITH YOUR USELESS ASS ANYMORE.

(Rant directed at project manager more than dev. Don't know which is to blame, so blaming PM)

In my current work, I have two systems to work on (let's name em Systems A and B). Both basically do the same thing; both allow users to book facilities available to them.

System A is already in production. My job is to fix any bugs that come up on said system. System B is an improved version that they wanted me to develop. This would follow a different framework etc. I am already halfway through this system.

Now, here's the fucked up part. The code for system A is a massive clusterfuck. It has unused commented code dated back to ancient times where men had the brain of an ape.

And don't get me started on the fucking logic. One part of the code was to retrieve and display the timeslots available for a chosen facility. The code to do that alone takes up 500++ fucking lines, filled with ajax commands, html manipulation and commented, unused codes..AND THAT'S JUST THE FRONTEND!

The fucking backend was not a problem of smelly code anymore. Nope. It was like a programmer had code diarrhea and shat his backend code all over the project. If I had a pin board, I would have made a crazy wall just to understand what some fucknut was trying to achieve.

Anyway, my supervisor told me to fix some bugs on System A. Knowing how the code was, I told her that I could refactor the code. Since I've already achieved that function on System B, with a shorter and cleaner code, I could just copy that and use on System A. But nope. She SPECIFICALLY told me to just "do whatever to fix the bugs. I don't want to waste time on System A." Okay. Makes sense to me. Whatever. I didn't wanna fuck my head up looking through that mess of a cesspool. So, I came up with a few hacks, not thinking of clean code and fixed whatever bugs there was. I then just pushed to the repo (after testing of course).

This bloody morning, supervisor came in and gave me more bugs to fix. When I thought she was done, she said "Hey. I saw the fix you made to the system. The bugs are fixed but the retrieval of the timeslots is now pretty slow. Could you see what is the problem?"

Slow.. She said that it was slow. And asked if I could fix it. I already told her what the problem was and she did not want me to waste time on it. But she wants me to fix it. WHAT THE FUCK IS WRONG IN HER BLOODY HEAD! I SWEAR TO GOD... UGHHHHH I swear I was already waterboarding her in my head. YOU WANT FAST?? How bout fucking allowing me to refactor the code?? Fucking shit head. I think I should take up yoga.

Messaging me at 4:30pm on a Friday about a high priority issue currently in production.

My reply: a link to the code review from 2 months ago that literally explained the problem and what to do to fix it. That got implemented. Then removed. For some reason...

Feels good.

I just saw a LinkedIn post where some guy suggested to fix gender bias in Google Translate by a few lines of JS code replacing every "he" or "she" by "he/she". Damn, give that man a Turing award, he solved the problem of biased models!!!
I love that his solution is completely contextless and will allow men to finally have periods and give births. Also, that the idea of bias embedded in models in general is completely lost on him.

Helped the designer fix a small JavaScript problem. She called me a God.

I'll take it.

That's good, Windows; don't actually fix the problem, just restart it... 😐

Come in. Edit one line of code. Fix the problem. Walk out feeling like a God.

When ever someone asks me to fix their PC I ask them to sit down next to me so I can show them how I did it. First thing I do is open up Google search the problem then look them dead in the eye and smile 😂😂😂. I Then proceed to implement the fix from the first page of results. I don't get many repeat requests... I'm Such a passive cunt.😂😂😂

was a member on a web developers group on Facebook.

someone posted a question:
- I am getting error 500, how can I fix it (yes just like that, no error message, not even what technology he's using)
comment 1 : how can I build a website please? (I mean, wtf, you can at least post a separate post)
comment 2: check your database, MySQL has problems bla bla ( yes, don't know how he guessed that ia the database is the problem, and who tell you he used MySQL anyway??)

Me: what the hell am I doing here?
*Quit the group*

Man I really hate it when people think that coding doesn't take any concentration and can just interrupt you while you're thinking about how to solve problems

So the other day I was working on how to solve a problem with filtering data with JS, and I had to urgently update one of our pages on our website. I had to update that page according to the content of a Word file, which I didn't check how long it was.

About 15 minutes later everything was ready and published, so I set myself back to my problem.

I get an email from her, "you mixed up things" and she showed up in my office. "There are four pages in this word doc and you copied wrong parts", I was like "ok, I'll fix it". Fixed it two minutes later, went back to code.

Received another email, with another subject, again with another problem. Start getting pissed off for being interrupted for nonsense. Fixed it instantly and put my manager in the email loop so she is aware my other colleague pisses me off.

And again, another direct email "can you fix this?!". I started ignoring her requests because I need some work to be done, and I already lost 2 hours. Got again interrupted by her personal visit to point me which things are wrong, repeating everything twice as I am stupid to her. Man I can't code in peace. I fixed her shit, exactly as she wants and decided to pay my manager a visit to tell her I'm really pissed about being interrupted all the time.

Five minutes before the end of the day, she comes panicking in the office about ANOTHER WORTHLESS issue. Told her it's nothing and went away.

Day is over, thought it was over - a whole afternoon spent correcting her fucking page that gets 10 visits a year.

On the next morning, "there is something wrong with your form, can you check it?!!?" with an attached screenshot. FFFFFFFFUUUUUUUUU STOP ANNOYING ME WITH YOUR FUCKING SHIT CANT WORK ANYMORE. PUT YOUR FUCKING PAGE RIGHT UP YOUR ASS AND FIX IT YOURSELF.

She doesn't have any access to the back end.

Guess I'll have to fix it then...

Studying Multimedia Arts, we are required to take a couple of courses in basic web development. (PHP). Since its known as new media grrr 🙄

Coming from a webdev background, I have no problem understanding PHP. However other designers in my course do.

A friend messaged me asking me how to fix a problem while in the dev environment. She tried explaining her problem without any of the terms we use in our general communication. You can read the conversation below.

Jr: I'm having a problem with my environment, can you help me?

Me: Sure! Did you switch to the latest Ubuntu LTS
so that your environment matches the rest of the dev team like you were asked to do the last 3 times?

Jr: No, I like Windows better because linux is too complicated. Can you just figure out how my environment is suppose to work and than fix what I did wrong please?

Me: No. Let me know if you ever need help with the our standard dev environment. Good luck!

I hate it when you CTRL-Z half way, try to fix the problem from that point and realise you fucked up. Try CTRL-Zing more and realise you fucked up your chances to get to the point you wanted :). Every single time.

"There is a problem with A, could you check it out? It's urgent for the client"
Me: Okay, just open a ticket for it too.
*Working on A"

After about ten minutes:
"Hey, there is a small problem B and it's also urgent for the client, we need you to check it out"
Me: I'm working on A and you are yet to open a tick... (Interrupted)
"But it's urgent and it's a small fix, we can fix it and push it to prod, A can wait for a bit"
(Since when is it a "we"?)
Me: *sigh* fine, lets see what's B is all about...

*After going over problems C to Z*

"Why isn't A ready yet? The client's mad and it was to be ready as of today"
Me: Because you had problems from B to Z and they were all urgent according to you so after each request you asked of me I had to postpone A with you knowing about it.
"But A is for today!"

FUCK YOU, YOU WORTHLESS WASTE OF JIZZ! YOU RAN TO ME FOR EVERY GOD DAMN URGENT PROBLEM YOU HAD FROM OUR SHIT OF A CLIENT AND INSTEAD OF TELLING ME THE PRIORITY YOU JUST THROWN IT ALL IN A RANDOM ORDER!
FUCK YOU! I WISH YOUR FATHER WOULD'VE SHOT YOU OUT THE WINDOW INSTEAD OF INSIDE YOUR MOTHERS CUNT!

Me: ya hi, we integrated with your API and I'm receiving error x
Provider: ok we'll disable validation, plz check
Me: ya it works, what's the problem? I used a GUID for id and I'm sure it's unique, here is URL and request body
Provider: you have something wrong in your implementation. Fix it and it will work
Me: aaand what's the wrong part of my implementation?
Provider: id is not unique, fix it. *Hangs up*

I sometimes sit and wonder, how and why does this kind of people get hired, FOR FUCK SAKE YOU ARE THE PROVIDER AND YOU DONT KNOW WHAT THE FUCK IS WRONG!
fucking useless ...

Boss: I don't want you spending more than 30 min looking into the problem.

Me: ok

Go back to desk and read or watch some cs training. Maybe related.

Go back to boss.

Me: going to take (over estimate tome) to fix.

Boss: ok.

Go back to desk and fix in less time than estimated.

Look like gold.

Manager: "<third-party vr app> isn't working. Think you could fix it by tomorrow?"

Me: "I can't fix it without the source code."

Manager: "Didn't you install it?"

Me: "I did, but I'd need <third-party>'s source code if you want me to make changes and that problem would probably take at least a day to fix."

Manager: "Can't believe you don't have the source code. Aren't you supposed to have your code available?"

(Just....)

My head hurt today when I heard this: "We could not reproduce the problem but we put in a fix and are pretty sure that it will fix the problem."

Me: *has problem, goes through hours worth of crazy complicated troubleshooting and tests to try and fix problem*

Literally anyone: have you tried the that super basic thing that you're supposed to do every time you start?

Me: oH GoDdAMMIT!!

How I feel when my family says "Sure you can fix the TV! if you can make a video game, this shouldn't be a problem."

Just spent 10+ hours refactoring a code, and at the end I've figure it out a one line fix to the problem... just wasted 10 hours of my life.. :)

You know what's worse than hell?

Your non-technical boss thinking he knows coding.

In the middle of night you are going to fix the problem he created, because he messed it in live server.

You know what grinds my gears?

Those people who ask about a problem on stackoverflow, github issue, or other sites and then reply:

"Never mind, found the problem!", Without telling what was the problem and did they fix it.

Fuck those people.*

*Not literally.

"PLEASE COME QUICKLY OUR INTERNAL NETWORK IS FUCKED!
-Uh, mam', could you describe the problem?"
Spent an hour, trying to fix this "network issue". Basic level 1 and 2 support. Can't connect using RDP on the server. No teamviewer either. Unplug, replug everything. Restart the server, the router, the switches. I knew that it was something dumb. I spent 3h on the highway.
To find.
That the fucking.
Ethernet cable.
Was plugged oN THE MOTHER FUCKING ILO PORT! FUCK HP, FUCK THIS, FUCK ME BECAUSE I SHOULD'VE ASKED FOR A PHOTO.

"It's fixed, mam'. Did you touch something when it was working?
-Uh, no, I swear. Also, could you please take a look at our printer? It's not working. It was out of ink so I changed the cartridge yesterday, but today it's not working!"

The cartridge was not inserted correctly.

Then she nicely made me a coffee, thanking me for the fix and asking what the problems were.

Just kidding.

!rant

Me: sudo apt-get update

PC: Noope. There is a problem with a package.

Me: Ugh... ok I'll fix it. *20 minutes later* Fixed. Sudo apt-get update

PC: Noope, the package cache file is corrupted.

Me: GO FUCK YOURSELF LINUX OMFG.
Oh, I fixed it.
I LOVE YOU LINUX.

You know when somebody complains about a bug in your software at a meeting to everybody, you go to their office, find out that the bug is actually an user problem, and then on the next meeting, when asked about the bug the person reports "we fixed it" and you correct them, explaining in detail how there was nothing to fix because the problem was completely user driven?
I love these moments

Sales: "There is a problem in complicated feature A, in a client system!
Dev: "What is the problem"
Sales: "I don't know exactly"
Dev: "which client system? What version is installed?"
Sales: crickets.
Dev: "Do you a Jira ticket, or an email with more details?"
Sales: "It is urgent that we fix the problem ASAP!"
Dev: "what problem"
Sales: "The problem! I talked to the VP RnD, So he can make sure you are on it!"
Dev: "What exactly do you me to fix"
Sales: "The Problem!"

Classic Wordpress:

1. Find a problem
2. Throw 2 to 6 plugins on the problem.
3. Admit, that they don't fix the problem either.
4. Implement some crappy workaround yourself.

But: It could get worse. You could use Joomla as CMS. Same shit, but without the available mass of plugins.

Friends' Boss: You're one of the programmers, right?
Friend: Yes sir.
Boss: I need you to fix this layout problem for me.
Friend: But sir, I'm a back end programmer, I hardly know anything about style stuff...
Boss: You're a programmer, you'll figure it out.

That's not how it works, that's not how any of this works.

The student life smell is strong with my Desktop too,
and no I don't have a problem I only drink and smoke socially also when a bug takes longer than an hour to fix...

Which is most of the time

Okay I might have a little problem

Urgent email, there's a problem. Fix the problem instantly and email back. No fucking response.

analysing a database problem and writing a 4-line fix: 5 minutes.

preparing a foolproof manual for the manager on how to apply the fix: 15 minutes

writing a manager-level explanation what the fix does: 30 minutes.

explaining it to the manager: 30 minutes.

writing a _detailled_ explanation why we need the fix: 60 minutes.

explaining it to the manager again: 30 minutes.

figuring out why our progress is slow:

_priceless_

Me starting a project: Okay I'm stuck with this project I'll just shelve this for now

[3 weeks later]

*comes back to project*

*find a solution with problem I came stuck with*

WHAT THE FUCK BRAIN WHY DID IT TAKE YOU 3 WEEKS TO HELP ME FIX SHIT WRYYYYY

Production crashed literally 5 minutes after I went to bed. Collaborators couldn't fix the problem as they had to reset an API key only my account could access. They tried calling me but my phone was muted. Woke up 5 hours later only to realise it had been down all night.

Whoops.

Windows update fails with error 0x1235

Me in Technet: Hey, ms, i got this error. How do i fix it?
MS: Install the Troubleshooting for Windows Update and follow the instructions. Before that, create a system restore just in case. Also, if the problem persists, go to your boot menu -> troubleshooting options and follow the instructions.
Hope it helps.
Found it helpful? Yes No

Other random people: just rename $WINDOWS ~BT to anything or delete it. Then continue the process.

.
.

I followed the random people advice and worked.

Fuck MS.

PM: Hey listen, client sent us his feedback about the app that we need to fix, they wont take time.
Me: Sure no problem.

5 Minutes later:
*Receives email*
*checks email*
15 easy tasks that take not time to finish BUT they are put inside ONE FUCKING TASK ON JIRA! WHAT THE ACTUAL FUCK IS THIS SHIT! 15 IN ONE YOU DUMB FUCK!
MOVE YOUR LAZY ASS AND WRITE EACH IN ITS OWN MOTHERFUCKING TASK!

Another reason on why I hate humans -_-

I hardly even know javascript, but I was able to identify and fix a problem in my Father's corporation website. Should I be worried, that the developer working for him wasn't able to do so?

I spent the last 3 months trying to hire new developers for my team. I found someone experienced who is great and a graduate, who is, well, a graduate.

For some reason he thinks he knows everything about our framework he has never used and seems to think he knows how everything works in our codebase which he has never seen.

That’s fine. I’ve had my share of cocky developers.

But what confuses me is that when I ask him what critical bugs are left, he reels off two significant ones. I ask what it will take to fix it. Of course he says he knows how to fix it. So I say great. Then fix it and let’s move on to a more fun part of our project.

Suddenly he didn’t know where he problem was and so I told him he had to investigate and come back with something concrete.

It’s just frustrating managing this developer who is deceitful.

Local time: 10:45 AM

I get a call from a customer. "My computer isn't working," she says. "I can't get to Google."

"What does it say?" Ideas swirl through my mind as I ask the question. I've seen this problem before.

"'Your connection is not private,'" says she. "I just want to buy a program."

I instantly know what the problem is.

"What time does your computer say it is?" I say it calmly, almost with a knowing smile. Yes, this has to be the issue.

"Um... 1:40," she says, a drip of confusion in her voice.

"That's your problem," I say. "Just fix that and you'll be good to go."

The problem was resolved and all was good.

I just LOVE how our service desk takes emails and reformats the fuck out of newlines so they look like

Hi

.

problem is fix.

.

kywbye

.

mr. dev

Certified Enganeers: 0, Internet Connectivity Issues: 1

Those idiots couldn't even understand why I'd connected a second router (a DLink DIR 816) for better WiFi than their default garbage modem/router. And one of them told me that he'd login to the router by "putting the address in Google" (and proceeded to type 192.168.1.251 in the search bar, after I explained to him that Firefox was a browser too, just like Chrome -.-)

And they didn't even fix the problem, which is most probably on their end since everything checks out here. Brilliant. More shitty 3G/4G for me.

YOU CERTIFIED PIECES OF CRAP

When you spend an hour trying to fix a problem... And the fix turns out to be so obvious

OK, so I was making this website for a university event. After publishing it, I start getting calls that the registration form isn't working. So I review the code and fix the problem. But when I push it to production, the problem still persists, all this while the event management is breathing down my neck because they can't get any registration! kept on trying for the whole fucking day, switched off my phone and went to sleep! The next morning, I find out, I had been pushing the old version of the file! Yes! I felt incompetent and stupid!

I've been a part of this industry for over two decades, found myself scraping and clawing my way up, recently leaving a high paying position to create my own company; in an attempt to fix the things I feel are severely broken within the ones I've worked for in the past.

Sometimes, we are challenged in ways we never thought we would be. And, it should always result in the improvement of something we never thought would be possible to improve.

There's a certain beauty of hitting a personal impasse. Because it allows you to choose a better path for yourself - which is a key element in accepting and conquering any one of life's many challenges.

So, just remember, we are - by nature - problem solvers. So what the fuck would we do, without a problem to solve?

So this is what happened!
It was a rainy Friday, I was asked to add a quick bug fix to a js application, I spent my Friday coding, testing ..., baam the patch is ready ... I wrote a nice commit message explains the problem and the fix but I didn't push the code.

On Monday the fuckin code disappeared, no commit no code no nothing no trace ... To be honest I don't know what happened. I rewrote everything on that Money morning (you can only imagine how pest I was)

I use vim with tmux.
I have done everything I could to figure out what happened to that commit, I even doubted If had did wrote the fix that Friday, but it's not possible to forget few hours of a day
I checked my commit history on the different branches i did everything

No trace ...
Conclusion
My machine is hunted ...
Or I have multiple personalities and one of them is a programmer and he is fucking with me

My most satisfying bug fix?

I found a core concurrency issue in this gnarly homegrown ORM and reported it to the lead devs, who (very defensively, having written the damn thing) argued that it would never pop up in a prod environment and I was stupid for even bringing it up. Theoretically, this bug could cause pretty much every foreign key to be assigned to the wrong parent, but only if multiple instances of the application were open/running at once. They were so certain it would never happen on live that they explicitly instructed me not to fix it. After all, this bug had been active for many years on a previous project and nobody complained.

Problem was, that previous project was something that only a single user had open most of the time (think: a manager). The new project was something that would be used by multiple people at the same time (think: all the employees). Once we released this new-project-with-old-orm, it didn't take long at all for our customers to start complaining.

After that, they let me fix the bug. :)

Failure is not the problem.

Problem is not admitting and accepting that you failed.

Problem is not learning from your mistakes.

Problem is causing the same damage over and over again.

What's worsens the situation is defending the dumb act.

If you cannot handle failure then not only you stagnate your growth, but you also negatively affect people around you.

Mistakes make you perfect only when you fix them.

A project manager, a computer programmer and a computer operator are driving down the road when the car they are in here a flat tire. three men try to solve the problem

the project manager said: let's catch a cab and in ten minutes we will reach out destination.

the computer programmer said: we have drivers guide.I can easily replace the flat tire and continue our drive.

commuter operator said: first of all turnoff the engine and turn it on again. may be it will fix the problem.

suddenly a Microsoft engineer passed by and said: try to close all windows, get off the car, and then get on and try again.

Someone I know quite well just told me that they have a hard drive with a S.M.A.R.T warning and "the internet says" that he can fix the problem by running this amazing built in windows tool called "chkdsk" (he literally learned about this today, as a long-term windows user) or by reformatting the drive.
I've told him that neither of those methods will work, since it is a hardware fault that is being reported by S.M.A.R.T.
He said that there is hope that it'll work, since someone on the internet said so.

ಠ_ಠ

Maybe not worst, but most frustrating. One of the systems I helped maintain at my first job had a few different bugs that caused bad data in the database. The "solution" to the problem was to write SQL queries to directly fix the production data. This would take one member of our team (it rotated weekly) about an hour every day to fix because there were literally dozens of these errors.

All the devs knew that we could identify the root cause and fix it in, probably, 3-4 days tops. Management would never approve the time because it would take longer to fix the root cause than it took to fix the data.

I worked at that company for 7 years. The bug was there when I came on, and it was there when I left.

This was some time ago. A Legendary bug appeared. It worked in the dev environment, but not in the test and production environment.

It had been a week since I was working on the issue. I couldn't pinpoint the problem. We CANNOT change the code that was already there, so we needed to override the code that was written. As I was going at it, something happened.

---
Manager: "Hey, it's working now. What did you do?"
Me: *Very confused because I know I was nowhere close to finding the real source of the problem* Oh, it is? Let me check.
Also me: *Goes and check on the test and prod environment and indeed, it's already working*
Also me to the power of three: *Contemplates on life, the meaning of it, of why I am here, who's going to throw out the trash later, asking myself whether my buddies and I will be drinking tonight, only to realize that I am still on the phone with my manager*
Me again: "Oh wow, it's working."
Manager: "Great job. What were the changes in the code?"
Me: "All I did was put console logs and pushed the changes to test and prod if they were producing the same log results."
Manager: "So there were no changes whatsoever, is that what you mean?"
Me: "Yep. I've no idea why it just suddenly worked."
Manager: "Well, as long as it's working! Just remove those logs and deploy them again to the test and prod environment and add 'Test and prod fix' to the commit comment."
Me: "But what if the problem comes up again? I mean technically we haven't resolved the issue. The only change I made were like 20 lines of console logs! "
Manager: "It's working, isn't it? If it becomes a problem, we'll work it out later."
---

I did as I was told, and Lo and Behold, the problem never occurred again.

Was the system playing a joke on me? The system probably felt sorry for me and thought, "Look at this poor fucker, having such a hard time on a problem he can't even comprehend. That idiotic programmer had so many sleepless nights and yet still couldn't find the solution. Guess I gotta do my job and fix it for him. I'm the only one doing the work around here. Pathetic Homo sapiens!"

Don't get me wrong, I'm glad that it's over but..

What the fuck happened?

Past two days one of the senior devs has been complaining to anyone who will listen about a UI assembly containing 'hard-coded' references to a third party component causing several builds to break. The developer who added the telerik component probably had no idea the reference is pointing to his personal directory instead of a relative path. Easy fix? Uh...yea...but he just ranted to our boss for about 10 minutes about he has no idea how to fix the problem and the TFS build failure holding up his other projects.
WTF!? You fracking know what the relative path is!...just fracking change it and move the frack on.

The drama this drama-queen keeps spewing out is driving me out of my mind.

I had this weird dream(emphasis on dream)

I was in a resort in bali waiting for my drinks and this cute girl comes over to my table.

Me : omg finally i can get a girlfriend
Me : hello beautiful
Her : hey i have this problem with my website *shows the messed up site with no divisions/containers * "can you fix this?"
Me : okay ;_;

PS : i started learning css, html and 2 other web technologies a week ago, and this is already happening to me, should i quit?

So we've been working with a VM at a university course I'm taking during semester break. Keyboard layout was QWERTY instead of QWERTZ, and I'm not used to the first layout, but no problem, I can fix that.
Or so I thought.

So I spend nearly half an hour trying to configure the VM to use the desired layout without altering the Ubuntu instance that much - only to then suddenly discover a small USA flag in the corner of the panel bar which could be changed by clicking once to the German flag.
This also changed the keyboard layout instantly.
So, yay, I guess. D:

I can only imagine what goes through clients’ tiny brains. Do they really think: “oh I know what will get shit done, insult the developer, his work, and demand things be fixed while saying the whole system is broken even though they have multiple times in the past demonstrated that it was either me using it wrong or an extremely quick and simple fix. I also have a problem with a few listed items in particular not the whole system, but I’m gonna insult everything.”

Fucking rude fucks!

Sometimes I feel people underestimate us.

During all my life, people has asked me if I can fix their *any device* because it goes slowly/something doesn't work.

But, of course, for free. Because they think the only thing we do is pushing 3 buttons and everything is done. They think everything solves itself easily.

Then is the fact that we should be able to fix everything always. Even if the hardware is broken. Even if there isn't any way to solve the problem.

I think we deserve a little bit more from society. I don't expect people to understand what we do but at least something better than the guy who formats your computer when it starts to go slow.

(Maybe I'm the only one who feels that way or it's just where I live, idk)

I'm not yet a programmer, I'm still learning. But is it normal to get so frustrated when I can't find a solution to something and start feeling totally useless?
It's funny because after a sleep I sit down again and usually fix the problem

Me: This is a good article about a CSS problem I always have and can never remember how to fix. Imma bookmark that.

Me, the next time I have that problem: Dang. Why doesn't this work. Better Google it.

"There's a problem with the app, can't you guys do something about it? It's wasting my time, aren't you gonna fix it already?"

Has been secretly working on a complete ground up rewrite which solves all the problems and reveals it to surprise and relief.

Web dev prob:

When you modify a code then refresh your browser, It doesn't change anything and you think your code has the problem, Modifies 100+ lines and refreshed the page, still nothing happens. Asked someone about it, Fix? Fucking cache! Fuck you google chrome!

Only god knows how much I hate people that give 1 star and doesn't want to explain the problem and allow me to fix it.

Dear mom,
Good for you you have so many contacts. Lovely. But when you visit someone and they tell you they have a problem with WhatsApp - or anything on their device at all - DON'T YOU EVER PROMISE AGAIN THAT I WILL COME TO THEIR HOUSE TO FIX THEIR PROBLEMS. I already ate enough candy today. And if they were to give me money (rare, we're in the Netherlands) I still couldn't care less. If you're too stupid to fix the problems on your phone you probably shouldn't have any phone at all.

Look, if it's my grandma who's kindly asking me whether I'd sometime like to look at her tablet to fix it, or I just happen to visit her (once in a few months): sure, I'll try my best. But for a stranger I haven't heard about who just got here? NO. I don't know you so I honestly couldn't care less about your problems. Go ask your own grandchildren.

So, a friend of mine just got a NullPointerException from his shitty Java code, and decided to fix the problem by catching the exception.
Great fix bro, real smooth..

The problem being a dev at a big company (around 1000 devs) with huge codebase (I mean huge, tens of thousands of modules, if not millions) is that, as many hands touch the code of a project and deadlines are always short, not everyone care about changing the documentation afterwards.

This translates to double the work everytime you need to fix a bug or something as you have to quickly reverse engineer the modules to understand it - the documentation often reflects an old version and it messes things up much more than it helps you out.

A plain computer illiterate guy rings tech support to report that his computer is faulty.

Tech: What's the problem?

User: There is smoke coming out of the power supply.

Tech: (keeps quiet for the moment)

Tech: You'll need a new power supply.

User: No, I don't! I just need to change the startup files.

Tech: Sir, the power supply is faulty. You'll need to replace it.

User: No way! Someone told me that I just needed to change the startup and it will fix the problem! All I need is for you to tell me the command.

Tech support: 10 minutes later, the User is still adamant that he is right. The tech is frustrated and fed up.

Tech support: (hush hush)

Tech: Sorry, Sir. We don't normally tell our customers this, but there is an undocumented DOS command that will fix the problem.

User: I knew it!

Tech: Just add the line LOAD NOSMOKE <nosmoke> at the end of the CONFIG.SYS. Let me know how it goes.

10 minutes later.

User: It didn't work. The power supply is still smoking.

Tech: Well, what version of DOS are you using?

User: MS-DOS 6.22.

Tech: That's your problem there. That version of DOS didn't come with NOSMOKE. Contact Microsoft and ask them for a patch that will give you the file. Let me know how it goes.

1 hour later.

User: I need a new power supply.

Tech: How did you come to that conclusion?

Tech: (hush hush)

User: Well, I rang Microsoft and told him about what you said, and he started asking questions about the make of the power supply.

Tech: Then what did he say?

User: He told me that my power supply isn't compatible with NOSMOKE.

I've became a better dev/sysadm since I've got a girlfriend. She has no freaking clue what I am doing when I'm working or sitting in front of my laptop. But she's often interested in the things i'm talking or ranting about when somthing doesn't work out like i've planned or some stupid problem occurs that I'm not able to fix. I am so glad i've got her. :)

Just because I know how to program doesn't mean I know how to fix your goddamn computer. We have an IT support team. Call them!

Don't come to my desk asking about a computer problem, then stand there with a vacant stare when I say I can't help you. I've given you the support team's contact info several times already. I assure you, they specifically get paid to configure your emails, install printers, setup your VPN, etc. Now where the hell was I at...

Yesterday my cousin called me to fix his scanner, he said that it didn't work anymore. When i went to his house to check it out, the scanner worked properly! In the 99% of cases, the problem is between the device and the chair

On the nth day of Christmas, my true love gave to me:

1 misconfigured autoscaling group
200 unnecessary servers
29 urgent emails
3 support teams that would have fixed the problem in an hour of anybody had bothered going to them first

Ugh. Idiots. Somehow the whole issue was caused by a single full hard disk, which caused database transactions to fail, which caused the group to scale out and spin up new instances, which didn't actually fix the problem so it kept scaling until it hit the limit and then continuously failed to create new instances for several hours straight, generating loads of notification emails and generally causing problems for everyone involved.

Working on building responsive emailer for a client.

Client: the emailer doesn't seem to work with our email system.

Me: can we have access to your system to do some tests?

Client: No you are not trained in it.

Me: well how are we suppose to fix the problem?

Client: Just keep trying

Me: ......

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

Friend: oh so you are a programmer?
Me: yeaaa..
Friend: great! Im having problem with the wifi connection on my phone.. Can you help me fix it?
Me: (( _ _ ))..zzzZZ

Sometimes your music app knows just the right song to play.

Story:
Production program was working (has been for a long time). But suddenly it starts failing. I spent a long ass time trying to see what went wrong.

Problem:
Security update on the server 🙃

Now I've got the client, his minions, and the users emailing me to fix this. But I didn't start this fire!

Song: We didn't start the fire, by Billy Joel

Sometimes at the end of the day if a solution to a problem seems inefficient I just leave the task rather than writing buggy code. It gives me a day's time, away from the screen, to come up with much better and elegant solution which I eventually code up the next day.
After years of experience I have realised that its better to wait for a day and not write inefficient code rather than trying to fix a hell lot of bugs later.

So a server goes down and being the only person who can recover it, I get started, whilst doing this the boys sits right next to me (6 inches) and starts asking what caused the problem instead of letting me get on and fix it, then complains the outage was too long.

I don't need you to reiterate what the problem is. I am aware. I was the one who told you what the problem is. Via email and Slack. Why do you keep restating it to me like you are the one who figured out? I know the table isn't syncing with the third party object. I'm trying to figure out WHY. No amount of "I'm pretty sure the sync process is broken" will trigger a solution. Stop coming into my office every 5 minutes with a new "revelation" that wasn't even your own. This isn't my code, and since the owner of said code is not here to fix it, I have to spend some time figuring out how this damn thing works. SO PLEASE, FOR THE LOVE OF GOD, LET ME WORK SO I CAN FIX THIS

Yesterday night, pushed code that work normally to prod server, website down, internal server error, too many connection to MySQL server, tried to fix it for 4 hours, nothing to do, removed the new code, still the same problem, in my head, I told myself that I'm not good at programming (not the first time), send an email to the host, they tell me the problem is from them and they fixed it. And now I know I'm not bad enough.

Submitting a pull request seems a good way to end the week. That's what I love about (some) projects on GitHub; instead of just ranting about bugs or out-of-sync documentation, you can fix the problem and send a pull request upstream. :-)

I found weird that some developer never ask why when facing a problem. "What do you mean never ask why?" here some story.

Let's say a developer work with simple app. Laravel as Backend and Postgresql as Database. He face a problem that the app very slow when searching data.

In order to solve that problem he implement cache using redis but he found problem that it fast occasionally. In order to solve that problem he implement elasticsearch because he think elasticsearch very good for search but he found another problem that sometimes data on postgresql out of sync with data on elasticsearch. In order to solve that problem he implement cronjobs to fix out of sync data but he found another problem that cronjobs cannot fix out of sync data in real time. and so on...

Do you see the problem? He never ask why the app slow. Which part search the data? Backend or Database (Search in the Backend mostly slower than Database because Backend have to get all data on database first). Has the query been optimized? (limit offset, indexing). How about the internet connection? etc.

For me it's important to ask why when facing a problem and try to solve the problem as simple as possible.

How many of you drink (too much) or having a drinking problem? And did you try to fix that?

I'm sober for three months and the consequences are huge.

Some say Whiskey officially was a medicine. I believe in that.

All what i have learned: stopping cold turkey was and is not the way for me.

Love it when you try to fix a bug and realize the bug only occurs in debug mode.
No clue why, but also not my fucking problem, users ain't gonna debug :D

WTF IS SUPPORT FOR?

A: Can you help fix X?
B: Can you help Y?
C: I see Z just crashes, fix it.

Me (in my mind): Can you tell me WTF is the actual problem and what investigation you have done?

Why the fuck are we paying you monkeys?

My company should just pay me all your salaries, and I will write a monitoring system to send out these types of "alerts" in a month.

Was helping my dad with his Arduino project when I realized something beautiful about being a programmer.

I have never worked with Arduinos and I'm clueless about hardware stuff but I was still able to debug, go through documentation, example code and fix the issues.

Programming is equally about the passion, dedication and ability + curiosity to solve a new problem as is writing some piece of quality code.

I might have taken a while to realize it but it sure is a wonderful feeling.

My manager has explained in detail to me how to fix the problem I'm having. I know how to fix the problem. I just don't have permission on our servers to change the settings I need to.

Guess who does?

Im getting annoyed by the new layout of google. Hovering the sidebar will make a scrollbar appear but the main part of the site's scrollbar will disapear. This results in most content moving from their original place. Let's make a Stlyish script to fix this problem I thought. Guess what now somethings stay where they should be, but the things that were first on the right place have moved. Also this will make the header shorter. I'm getting more and more amazed how shitty some frontend devs are at google.
To fix one bug they, instead of solving the bug, tried to counter the result of the bug.

I do like the z-index of the sidemenu though (it's 2005, the year youtube was created)

CEO announced a bug bounty programme for devs to do stuff in their free time for additional cash.

Cash is decided by business people based on their idea of how complex the given problem is.

And it's not for bugs one could just find and fix. Only some fixes/features decided by them.

Like second shift.

Code review, intern style:

Intern: Here is my pull request ...
Colleague: I see a problem with x, y, z. Could cause memory leaks.
Intern: Oh yeah you are correct, i'll fix that in the next one.
Intern: *merged*

Had to fix a bug in flask App built by 3 ppl !
So I some how roughly figured out the code and was trying to fix.
The bug was
I click on submit, two times the record was entered into database.
(Second time, duplicate error).

So to figure out ,I just commented the code which inserts to DB!

Whola!
Now only one record is inserted!
I still don't know where it's actually inserting !, And IDC , problem fixed

Shall I boast about my skills!?😂

There is always that one guy.. who doesn't give a fuck about testing and thinks he's not responsible for them...
Le Guy: lemme just push ma new code maan
Jenkins: Unit Tests failed - pls fix
Le Guy to the one who cares about testing: hey fuck uu, ur stupid tests are failing... fix them its ur problem.
*sigh*

That happiness after you are so close to open the closest window and throw the pc, but you manage to fix the problem.

FUCK YOU GRUB I WON!!!!!!!!!!!! SUCK IT!

You ever spend a few weeks on a problem. Make little headway on it then get distracted and forget about it for 2 months only to comeback and fix/finish the entire thing in a handful of hours.

That was me today. Could not get something to work back in March. Didn't touch it till today. And just magically I knew what I was doing wrong before

Product and Design have a common enemy. Yes, you guessed it right, Engineering.

The former aim to solve user problems and focus heavily on aesthetics most of the time. While the latter actually does it.

As a Product guy, I admit that I absolutely hate the role these days because all that are asked to focus on is engagement retention conversion and other fancy metrics. Community has missed the entire point of why the fucking role exist.

On the other hand, engineering always asks the best questions. Focuses on performance and scale while periodically checking on tech debt. Yes, they suck at business or sales but when the solution works, things automatically make money.

I DON'T FUCKING CARE HOW BEAUTIFUL YOUR APP IS, IF IT DOESN'T SOLVE MY PROBLEM THEN IT'S RUBBISH.

Functionality and UX matters to more than colour scheme or fonts. Reason why Amazon is a huge. They are functionally solving a great problem while constantly improvising UX and not giving a rat's ass on UI.

Another down side to your fancy design is that the UI elements make things heavier. No wonder engineers have always been the best problem solver.

We lost our way. Tech world needs to go back a decade or two to fix the tech debt.

So I took over a project from another dev after he left the company and his project was currently in QA pending release. They were blocking it due to some issues around the persons information not appearing consistently. It turned out he wasn't persisting the persons information in the database with the actual record.

It would be as if when you ordered something on amazon and changed your address for a future shipment all shipments would show the new address. So it turned out QA had no idea how bad the problem was and they had pushed this issue to him to fix but he just wasn't fixing it.

When I reported the problem to my boss and due to the time constraints for release they authorized a contractor to come in to assist. I ended up writing a few classes and one table to persist the data and all of it was solved. I ended up fixing the problem in one weekend. Huge problem and I fixed it in just a few days.

FUUCCKKKK!! I need to hit smth. Or rant..

So that flaky ec2 issue.. These ec2s act as a shared environment for multiple apps. Our app is one of them. I have no access to those ec2s at all.

What I have access to is my app and some monitoring. Now the app randomly starts lagging while nearly idling. At the same random times monitoring stops completely and doesn't come back up. This happens to random app instances at random times.

Reached out to infra support, managed to get attention from the big boys [mgmt]. Today we got the fix deployed. I test it out -- problem persists.

I find this behaviour somewhat familiar. Managed to get some server stats from infra folks. Apparently cpu% is high as well as load avg [cpu queue]. Bingo! I know how to fix it!

So I write a long comment w/ all the commands and all the 'if that, do this'. Send it to one of the infra technitians

and I get a reply: 'we will apply cpu usage limitations to fix the issue'

wait... Cpu% limitations will do nothing but highlight the underlying problem...

'no, instances have high cpu utilisation which is causing those lags. We will limit cpu resources and it will be fixed'

oh ffs... Cpu utilization and cpu queue are VERY different things.. I tried explaining that to them like 7-9 times. And all I get is:

'yes, cpu utilization is the problem. We will limit it and solve the problem'

I would surely escalate all of this through higher channels if only I could get my hands on those ec2s and have a proof. But that is not happening and I'm forced to sit back and watch them break things even worse until they are out of options and mark my query as 'wont fix'....

Fuck that's frustrating....

*thinking to myself* so I've read about that new vulnerability 2 days ago that allows one to escape from docker container to the host... What if <...>

*PTSD kicks in* Hello darkness, my old friend... :')

At least after 5 years, this time it took me only few seconds, to locate the source of the problem, and fix it.

PS: fuck you javascript... STILL. FUCK. YOU!!!

Proudest bug squash experience?

Fixed a N+1 pattern bug on our web site. Wasn't a deeply technical problem, but I was proud to shove the fix up the arse of the developer who blamed me (and even got a VP involved) for the web site crashes (the N+1 involved his code calling a service I wrote) and none of the half-dozen other devs found it.
I really wanted to make a t-shirt with his initial 'blame' email outlining all the 'technical problems' with my service, and the fix was literally moving the service call outside 5 (yes 5) level deep for..each loops.

Today I solved the problem assigned to me by changing one character. Simplest fix ever. Except that this problem is not on my project, and I don't have control over this project, so I can't merge my pull request or deploy the code, and the dev that does hasn't answered email today, and he's not scheduled out, and he's not in his office. Whatever, I'm just gonna say it's fuck it Friday and call it a week.

Very senior colleague: *hits a problem that is a minor inconvenience*
VSC: "I have to restart this task, the two weeks I put into it must be deleted!"
Me: "You forgot to do *this* here, add this 1 line and it's ok."
VSC: *An hour of rumbling about the codebase*
VSC: *adds my fix*
VSC: "Ok, it works now, you can review again"
Me: *cries inside*

Why is it so hard for people (especially managers) to learn to work smarter not harder....

FIX THE GODDAMN PROBLEM CORRECTLY... THE FIRST TIME SO WE DON'T HAVE TO KEEP FIXING ITS BLOWUPS ON WEEKENDS....

AND STOP HIRING MONKEYS THAT JUST KNOW TO PRESS BUTTONS RATHER THAN DESIGNING FULLY FUNCTIONAL SOLUTIONS THAT DON'T BLOW UP OR LEAVE A TRAIL OF SHIT BEHIND THAT I NEED TO DECIPHER N CLEANUP....

Life sucks when you get an error which you have seen this error like plenty of times and when you start debugging it and run out of all the ways you have always followed to fix it and all those didn't fixed the problem.
With nothing left now to approach, wondering what may have gone wrong.
The fundamentals are shattered
...

It's almost 4 on a Friday and my coworker just left early. The only thing before leaving was to tell my boss about a problem in production...
Leaving me to fix it...
"Hey, I just heard about a problem in production. Can you fix it before you go?"
Not cool dude... Not cool.

This temporary hack will just temporarily fix this problem. We will come back and actually fix the problem later.

We never come back to fix it later. This shitty hack I made in less than a day that fixed the problem for the day "fixed" the problem for the next year.

Lesson learned that temporary structures and side projects will be there forever. Make them right the first time.

The fact that there's only two characters between "run this job every 10 minutes" and "run this job every hour on the tenth minute" was the fix for the particular problem i just spent 5 hours on :facepalm:

I've just spent half and hour trying to fix a problem when I remembered that Arch upgrades kernels in-place and I just have to reboot.
Because deleting the CURRENTLY RUNNING KERNEL is definitely a sane thing to do...

Recently got a new widows laptop, I was so excited.

Spent a free hours trying to fix the hard drive which is spinning at 100% making the computer slow... still haven't found the problem.

So I coded on a Mac instead

...and then I found 20 dollars

Has someone an idea why KDE Neon has this buggy text rendering and how to fix it? Google is not my friend with this problem.. It's often the text which is buggy but sometimes everything else is buggy too..

Boss: "You hardcoded the redirect uri in the code (Early on during development and forgot about it, because apple OAuth is a piece of shit), but don't worry I fixed it by hardcoding the uri with the production host into the config file where clearly all settings are fetched from the OS Environment variables at runtime. This will surely fix the problem in staging we have, no need to thank me"

the look of disbelief you get from non devs when you Google how to fix a "generic computer problem" they have asked for help with... as though it's your job to just know every minute detail

Me: *changes a long and complex calculation to fix old mistakes*

Program: *keeps outputting the same wrong result*

Me: *goes mad for a good hour trying to discover the problem by debugging it like a angry rat*

Also me after one hour of debugging: *discovers he never changed the output source of the function and it's still outputting the old result*

boss said: "we need create new version of our software. copypaste old version in new branch. so we will have dozens of versions and all of them online and working."
my question: "what if old bug will appear in all off 100500 branches? we will need fix all the versions of bug in different copies we have modified!"
boss said:"c'mon when we will get this problem then we will think about it. all the devs in world working on many versions. its easy."

your opinion?

once upon a time I went on vacation.

It was for 5 days and I went to Leh-Ladakh with my family. (Me, My big bro and my parents.)

It's a beautiful and cold place. Snow and High Mountain and no phone call from anyone.

It was supposed to be no call. But on the 3 days, I got a call from my junior and he said to me that server is not working and it's giving 404 error.

So I told him to go to Cpanel (It was client's server). After 1 hour I got a call back from him and he was not able to fix it.

So I had to open the Cpanel in my Galaxy Note 8, Open file manager, go through all the files and logs and fix it code in 2 or 3 files.

It took 4 hours to fix the problem. But that day I understood the value of my Note 8 and its big screen. Thank you, Samsung.

Note: The lake in the photo is Pangong Lake/

Devs! Heard about this thing called going to sleep without dreaming about ways to fix a bug?

Whenever I force myself to sleep whenever I get stuck on a bug or confused about the implementation of a feature and started dreaming about the approaches I can take. Most of the time I wake up around 2 or 3 am to try out an idea I had and most of the time it works.
Now I fear this is becoming a habit. Is it something I worry about or ignore since my problem is getting solved?

i understand and accept why some people prefer mac.

every mac i have ever used has shit the bed during normal use. while windows and Linux machines have too, however less frequently. unlike mac there is always something i can personally do about it to fix the problem.

i like having complete control over my computer and don't like the idea of paying a premium to be told how i can or can't use it.

We’re IT, Of course the problem is going to magically fix itself when we show up

Manager encounters problem, hacks a load of stuff together to "get around" the problem. Asks me to fix the issue. I spend a week tidying up what he'd hacked together, then change it so I encounter the problem.

A morning of probing later, the problem?

One of our servers is running 2 firewalls, so we were having network connection issues on just that server.

DFW the client decides to not renew the contract, and so their start hiring their own developers. This guy decides to fix a layout problem by putting everything in a table element, breaking a bunch of other shit he didn't test for before committing. Fucking end me now, please.

I have been at my job for four months. I do 99% of the research on a problem or a fix - another employee recognizes the remaining 1 % and looks like a champ.

when your family comes to you to fix every problem with their computer and you're too tired of explaining what you actually do, so you put on your most professional look and hope for the best

I'm new to javascript and I'm doing the freecodecamp. I was doing a challenge and I was looking everywhere how to fix my problem (I needed to use an API from another page) turns out all I needed to do was add the Jquery library, I've been stuck with this for HOURS FML

Working on this bug for a day. Frustrated Friday afternoon. Decided to explain to my manager and senior why I can't find a fix and while explaining it to them, I eventually figured out the problem and fixed it.

I just realized I used my manager and senior as rubber ducks.

Cars

I love classic cars because of their simplicity.

I don’t want to remove dozens parts, need computer or call support to fix simple car problem.

Mechanical solutions were good and reliable in some of the old cars so we can still renovate them and use them after 50-60 years, we won’t be able to do it with modern cars so we are in fact producing lots of waste.

Today’s car companies are ripping off their customers by providing overcomplicated solutions that prevent customers to repair a car on their own.
And don’t let me start about proprietary car software and protocols.

That’s a big world problem right now.

We are gating release of each sprint.

Today before 10:00AM I identified a major performance problem and asked devs to fix it (single if() will be enough as a hotfix). We're blocked until we have the fix deployed.

It's 5pm and we're still waiting for that 1 `if` clause to be added and deployed :)

A long day it was. Full of hopes and expectations, waiting for things to happen

Today, I was sad because of a problem that I could not fix for the past month. I was so desperate and disappointed that I seriously considered switching career. Then mentor helped me fixed it. To say that I went ballistic is an understatement, I went intercontinentally ballistic.

How is everyone's day going?

Yesterday, my boss asked me to solve a certain problem the company has with my code.
I tried reproducing it for a very long time but still couldn't manage to do it.
Ultimately (after my boss has been no help at all), I changed some stuff and sent the revised version with this message:
"I couldn't reproduce the problem, so here is a revised version with some changes that **could potentially** solve the problem you're facing."
She immediately decided that the entire company was switching to this version and thanked me. There is no way she tested it that fast. She just saw this might be a fix and didn't bother with the details. I have no idea if the update fixes the problem or even if it won't break anything else. I tried to explain the situation to her but she asked, "Are you saying this works on your computer?" and I was like "Yes, but..." and she didn't care about anything after the Yes, and I just know that when the problem will occur the complaint will be directed at me, and I'm sick of it.

You're stuck in a problem for hours. You light a cig and with the first suck of flame, it comes to you how to fix the problem.

It happens to me everytime.

Someone wanted to take a look to kde on Ubuntu 18.04 in my laptop, so did:

`sudo tasksel install kubuntu-desktop`

After rebooting and all did:

`sudo tasksell remove kubuntu-desktop`

and now I don't have GUI. The problem is that I can't also have network, neither by WiFi or ethernet. So I can't install packages.

The best way to fix that is to reinstall Ubuntu? Or there is a way to recover the ability to connect to network?

BTW, yes: "someone" was myself.
Shame on me 😔

CTO at my previous company think that wordpress based website is took a long time to load.
I suggest to use caching and fix ton of abusive query, He refused. He spun up more VM, upgrade the ec2 instance level to the max. Said that he resolved the problem. But the problem still persist actually.
Blame me for slow response website, blame me for late of deployment because data is not ready ( there's a lot of spam in there, we need to clean it before )
I left the company, Coworker said that he just install a bunch of caching plugin,
He made the website down for entire day and don't understand what is happening. Ask other developer to fix it quickly, to do unpaid overime
The site is back to bussiness, said to all team that he already fixed it.
Everything good happened, he claimed that it was his idea.

And the best part is : he put 'ssh' as skill list in his personal site

Whenever network issue is encountered,
Step 1:
Reset the router.
It fix the problem half of the time.
Step 2:
Take out the eth cable and plug it in your network admin ass.

My life was troublesome today, had to help a non programmer to run jar files.

The jar executed well from command line in Windows 10 but didn't work on double click.

Did all the tricks, registry edits, cmd commands and at last I found a miracle tool called Jarfix.

Just double click and all okay.

The root cause of the problem was 7zip.

This bug is reported in the Oracle bug reporting and they have closed it as " Will not fix" low-priority report.

Genuine question: Whenever an OS encounters a problem and I 'send' the report to help fix the problem, does anybody read that? Or windows just stalling?

So I have a job at a client to fix their system because the last systemadmin fucked everything up. One of the things I need to do is let the boss work from home.

No problem. I set up a vpn connection to work and everything just works. Except that the home network had the same dhcp range so that had to change.

I login on the router and literally everything is fucking locked. I call them and they send me a new router same fucking problem. So we bought an asus router so I finally can fix it.

QUESS WHAT THE FUCKING GARBAGE DOESNT EVEN HAVE BRIDGE MODE. FUCK KPN AND THEIR MODEMS.

When having to fix parts from an other programmer's code, do NOT concentrate on the small code expected to be wrong, instead read and understand the whole program around it!

Best practice:
1) Why is this code here
2) What does this code do
3) How does the code solve the problem

(just happened to me 😅)

We've told our client they can test their brand new distribution modul with a new test account already 42 times (not exaggerating, I counted). At least half these, we've sent also the test login data which they could use.
Just now, a new issue message from them says distributors couldn't see some data, we should fix the problem. Well, they already can't see those, but client has logged in with their own account again for testing...

Did you know that docker's ADD instruction uses "go-http-client/1.1" as user-agent when src is an URL?

I didn't. And since I'm unfortunate, enough so that this user-agent is blocked by my company, I've now spent twice the time it took me to write the whole dockerfile to identify the problem and fix it...

I love waisting my time for such minor things...

Trying to install Centos7 onto my proliant g6, red screen, try a fix, red screen, try another fix, red screen, finally find a fix that seems like it is the exact problem, screen dies can't see bios... god damnit.

Someone asks for help as to why their website isn't working, you find the problem and tell them, then they're like "no that can't be the problem". So you fix the problem and they ask "what did you do?"

"Programmers Know Everything"

Im writing this as myself cause, well this tends to happen to me alot!

When ever a friend or a friend of a friend has an issue with a website or just their computer they run to me, which is all fine but if I say "I dunno? I never heard of this issue so I do not know how to fix the problem."
Their response is normal "But dont you do websites? Surely you know how to fix a virus or bluescreens ?? "

So I'm currently "assigned" a task in which I need to fix a slow query problem, which isn't a big deal. The biggest problem is that the original team of this project haven't got any means to develop things on your local machine. Looking at their docs and scripts, it seems like everything is deployed to a dev server. But whilst looking for details for this server, I found out that the network team have decommissioned the server!

So my dilemma right now is that I can't test any of my fixes on anywhere besides staging, or possibly production! Inheriting projects is the bloody worst!

Repair printers... Somehow writing code translates to the ability to fix any printer problem in their minds.

Me - Ooo I've got this idea ! This will fix this "No ones" problem in programming.

(Thinking this will change the programming for everyone)

Starts Coding......

Few minutes later ...Searching stackoverflow for silly syntax errors.

...Finds a 2 years old project from some guy, who already finished working on the idea and answering question as "This is a bullshit idea!, Never try to make something like this."

Me - (Suffering from existential crisis)

boss: someone fix these it's not working *3 problems highlighted on screenshot*

problem 1: something went wrong when updating the data, i fixed it in a minute
problem 2: not our problem, send an email
problem 3: wait isn't this the task *boss* handles?

I feel like a fraud ...
So I recently joined a mobile dev company as an intern
I submitted the application
Got to coding interview passed the coding interview because thank god it was one of the sums i solved on geeks4geeks
Then came then interview did as best i could
Got the acceptance mail in next 10 mins
First day was chill it's work from home thing
Second day they gave me an app a previous intern had already build its layout and authentication code
But it wasn't working so I reported it so they told me to debug it so I found where the problem was occurring
Now I know the problem but i have no idea how to fix it
They gave me assignment to fix the authentication basically it's taking info creating a json and request an API call
But I feel i cant remember the concepts
I can't remember basic meaning of words the other day i forgot what SSID are
I just I don't know shit
And i feel like I'm going to get kicked soon
I don't understand what the previous guy wrote and i don't know how to fix it
Previously i have built my own apps but not like a real world project like this which works in regards to network management basically an wifi portal kind of Authorization application

I've seen far worse people doing what I'm doing, applying terrible practices and still being valued af.

Even if I do smth wrong after doing all the research and alternatives' analysis I know I'll do a proper post-mortem RCA, document it and learn from it, as a result I'll make a better choice to fix the problem and I'll know better next time.

I think I'm alright compared to them. So I don't wory about being an impostor.

Learning by good examples is a good approach. Learning by bad ones might be even better. The "good ones" are yet to fail and be replaced by better (or worse) ones. The "bad ones" are already failing and you can learn WHY you should not be doing it like that and HOW should you do instead to solve the problem.

Learning from good examples only works well if you know the back-story, all the WHYs and HOWs. People usually don't :)

Troubleshooting in Windows be like - " Well mate, you are fucked. Till the time we run a baseless scan.. relax ,take a deep breath ..Check your internet connection . .. for you are going to have to google the problem and fix it yourself...

That moment when you build your app around a clients development API only to find out their production API responds about 8x slower... I'm sorry, it's not my fault your API server takes 4000 ms for a SIMPLE response. My app isn't the problem. Fix your shit.

Inherited a codebase that implements its own word wrapping for receipt printing. Problem is it's putting an extra space at the end of each line.

I open up the implementation, expecting it to be a relatively simple fix, until I see this…

var regex = '.{1,' +width+ '}(\\s|$)' + (cut ? '|.{' +width+ '}|.+$' : '|\\S+?(\\s|$)');
return str.match(RegExp(regex, 'g')).join(linebreak);

What the fuck is XCode's fucking problem? This bullshit has happened so many times, and the only fucking way to fix this shit is by manually retyping the whole fucking thing!

once I have to code in a public train station’s restroom just because I have no place to sit and floor is not comfortable enough because people keep walking by distracting me,
So I cover the lid, pull my laptop out, use my phones hotspot connect to remote server to fix the problem.
The smell is not good.

Ahem id like two superpowers please ,

Then first one would be to telepathically nerf down parasitic ideas instantly, I could actually be the next superman if I had this.. Could save a lot of lives in the developer realm.

The second one is the power to instantly fix any kernel / driver / boot problem and make everything compatible with Linux