I built very involved code with multiple auth systems, async programming, business logic, error handling, and etc. I was asking for the missing environment variables during the call with devops and had a screen share going. Environment variables were the last thing I needed before knowing if it would work. I filled in the config and all the code worked perfectly.

The devs lost their shit. One suggested that I had somehow tested it beforehand because it is impossible that it would work the first time. “How? I didn’t have config details or access to any of the remote APIs until now.”

The dev lead finished the call with, “That was some big brain next level shit.” Then they went and reviewed and tested it after the call and didn’t have much to suggest besides naming nitpicks.

It was at that point I knew I was a hero to the other devs.

I've had two DevOps engineers ask me how I deploy new pipelines so quickly.

I show them how I automate the automation.

Just a couple weeks ago I felt a bit like a hero.

My boss, who seems to have only a vague understanding of realistic deadlines, for once made an error that gave me more time than I needed, not less. I was working on a feature that other work would rely on, so some people had to wait to work on their own projects until I was done.

My boss said it would be done in two weeks, but the only reason why it would have taken that long was because I'd have to submit a ticket to our identity management team to set up the SSO integration with our identity provider, and their turnaround time is two weeks. Or it used to be, but they've actually gotten really fast recently, and as I'd actually grabbed this feature from someone else who had to take a few days off, he'd already gotten the SSO stuff taken care of in advance. My boss promised two weeks and I finished in two days. The shocked silence when they asked for a status update in our next meeting and I told them I'd just finished it was music to my ears.

Sorta dev related.
I work at a service desk for an automotive supplier.
We've once hab out entire mobile phone system crash and for whatever reason, it won't let the phones connect, if there are more than 50 phones trying to connect at the same time. Kind of a problem if there are 400+ phones trying to connect.
My colleagues showed me what to do in order to get one phone to connect to our system.
It was basically: enter some invalid data on out webinterface, save, enter the correct data again and safe again.

It was too stupid for me. So i hacked an AutoIt script together in about 15 minutes, and let it run for the next half an hour. Showed it to my colleagues, they were excited and I went and got a coffee.

I don’t make people feel dumb from the doubts they ask.

Just had my last day at my current job last week. I got this amazing virtual card with 20-30 people telling me how amazing I was and how large of a difference I made. I’m not someone that seeks or needs validation, but to see those comments in writing really made me feel good and like I made a huge difference.

Debugged a complex bug at 10 PM, drunk and eating potato wedges, while on the phone with another drunk co worker.

Woke up next morning and had no memory of the fix.

Every day at work. I think everything might just burn down if I leave.

Tough one.

One of my biggest weaknesses is that I'm having trouble with positive feedback.

It's kinda self defense because positive feedback usually means that a negative thing will happen.

One of the moments where I feel like a dev hero is when I can just accept the positive feedback.

Fixed a bug today that I created over a year ago.
It made a machine start doing really fucked up things like running motors when it shouldn't. My boss, an expert on the system and the code, gave me some ideas to check. He couldn't understand why it was doing it either. So I started checking things and comparing to another piece of code that does similar things. I finally found a place where I had used a really sketchy pointer. I even knew it was sketchy at the time and put a ? mark in the comments next to the line of code. I changed the code to match another system that explicitly creates the object. Then I started testing the system and boom everything is working as it should. I talked to my boss and explained everything. He said it was an easy mistake to make. Internally I was saying, "But I don't make easy mistakes. I make hard mistakes!" LOL

Got to walk away from work for the weekend knowing that my other code is a lot more solid than I was thinking earlier this week. I was starting to second guess what could possibly cause this problem and thinking there could be culprits everywhere. Boss was happy problem was solved as he is going to be showing off the system I am working on in a month at a show.

Every time basically.

Coming up with complex Excel formulas.
Cooking products in a weekend.
Setting up and printing a shit ton of spreadsheets in a minute with a VBScript.

Yep, every time.

Never felt like a dev hero, just a jukebox hero.

I felt like a Dev Hero after losing both my laptop and my car from the deer encounter. Really needed that delicious sandwich from Dev’s Kosher Deli to unwind from the stressful event. The pickles are to die for...

Completed the project alone in one week's with clean code and backup. And Get 25000CNY easily.

Well it's an IOT project