Spyke
lemmy.world

My favourite is always;

Lemme quickly write this test, it passes great, if I make this little change it'll fail. It's still passing, damn.

89
danreply
upvote.au

The worst is when you expect an existing test to fail, but it passes, and it turns out the test wasn't actually properly testing the code. Fixing the test finds a bunch of broken edge cases.

57
lemmy.world

Then you ask questions about what the past person could possibly have been thinking. You wonder what logic path brought them to create the code this way. You check git blame. It was you.

42

Debugging. It's a whodunnit where the victim, murderer, and investigator are all you.^(apologies to Filipe Fortes)

21
lemmy.world

It's always scary when it compiles without errors the first time. Then you just know there's a logic bug or corner case in there somewhere.

60

It's always a logic bug that you will find the day after you forgot about how the code works.

3
marlowe221reply
lemmy.world

Nothing is temporary. Every script, patch, application, and duct tape MacGyver/Scotty inspired fix I’ve ever written will run for eternity….

20

The first "temporary hack" I ever wrote for my current job (~January 2014) is still in the codebase.

20

if you didn't intend for it to work and it's working then it's not working as intended

40

One time I stayed up late trying to fix a really complicated problem that I couldn't figure out. I was drinking. I got really drunk and fixed the problem. In the morning I couldn't figure out my own code. I had no idea what I wrote, or how it worked, but it did work. I just left it since it was apparently above my ability to fix.

6

"You know that temp shitty load balancer you wrote on your second month to get things up again. We still use it to this day." My boss last week.

5

Remember, every temporary solution is a permanent one! It's always spooky when it works the first time.

4

You reached the end

Something is broken... I know it.. | Spyke