I spent all day today trying to fix a bug...

[NikolaeVarius]

After 3 restarts of the service and a good 4 hours starting at debug logs trying to figure out why a process that runs every minute randomly skipped anywhere between 3-7 iterations of the run, I asked a senior engineer to take a look at it.

He restarted the service using the exact same commands as I did and the process started to work perfectly.

Why.

 

[Mayne]

coincidence and bad timing on your part.

 

[Atomic Playboy]

That's why he's the senior engineer.

 

[IronWing]

I spent all day today trying to fix a bug...

Those balls are so tiny and hard to reach.

 

[nakedfrog]

That's why he's the senior engineer.

Yep. That's how I got to a senior role too.

 

[GagHalfrunt]

The computer has developed sentience and is just fucking with you.

 

[Markbnj]

That's why he's the senior engineer.

This. It's all in the attitude.

 

[GrumpyMan]

Same reason when you take in your car to the mechanic because of that weird noise coming from the engine and it does not do it again until you leave the parking lot....

 

[dave_the_nerd]

*bro hug*

 

[SlitheryDee]

He obviously set it up to do that. Occasionally causing a few problems that only you can fix is good for job security.

 

[NikolaeVarius]

Same reason when you take in your car to the mechanic because of that weird noise coming from the engine and it does not do it again until you leave the parking lot....

Difference is that this problem has log files backing up my debug attempts and the issue can clearly be seen throughout the log.

But for whatever reason, it just happened to work properly again after that 4th restart.

 

[who?]

A trickster spirit was messing with you. I have seen a piece of equipment not start up until a maintenance person walked up to it and before he did anything it started working correctly.

 

[nakedfrog]

A trickster spirit was messing with you. I have seen a piece of equipment not start up until a maintenance person walked up to it and before he did anything it started working correctly.

Some people have this knack, others have the inverse, where something that's been working fine will screw up as soon as they get near it.

 

[GrumpyMan]

Some people have this knack, others have the inverse, where something that's been working fine will screw up as soon as they get near it.

That would be me and marriage......:\

 

[CoPhotoGuy]

Some people have this knack, others have the inverse, where something that's been working fine will screw up as soon as they get near it.

Yup. I have the knack as well....minus the social ineptitude.....


https://www.youtube.com/watch?v=60P1xG32Feo

I'm also good at telling non-senior engineers all the things they did wrong.

 

[SlitheryDee]

Some people have this knack, others have the inverse, where something that's been working fine will screw up as soon as they get near it.

Come to think of it I am always complaining about how everyone else in the world's shit is constantly messing up while I seem to have very few tech related problems.

I think it's more that I take the time to figure out how everything works and what I need to do to fix it. Otherwise I'd always find myself pounding a keyboard shouting "You're supposed to work dammit" rather than doing anything constructive. You gotta be willing to dive in there and press buttons until it does the right thing. You'll mess up a lot of shit on the way, but fixing all that can only increase your understanding of the program/device/etc.

 

[Elixer]

After 3 restarts of the service and a good 4 hours starting at debug logs trying to figure out why a process that runs every minute randomly skipped anywhere between 3-7 iterations of the run, I asked a senior engineer to take a look at it.

He restarted the service using the exact same commands as I did and the process started to work perfectly.

Why.

At the same time you were doing those commands, he was stopping it again to make you look bad.

That way, he knows his job will not be in jeopardy from someone lower than him.