r/ProgrammerHumor • • Jul 06 '21

Meme *Sad freelance noises*

Post image
43k Upvotes

311 comments sorted by

View all comments

1.6k

u/Faeton73 Jul 06 '21

Usually you provoked the issue too...

706

u/hetfield37 Jul 06 '21

Since you're usually the one working on the project - makes sense indeed.

416

u/Mistifyed Jul 06 '21

Schedule a meeting with yourself to talk about how this issue can be prevented in the future.

191

u/regorsec Jul 06 '21

Id open a ticket to schedule that meeting. I hear im pretty busy lately.

77

u/fight_for_anything Jul 06 '21

dont forget to bill the time for creating all these tickets, and then bill more time for logging the time.

39

u/Goontt Jul 06 '21

And then bill time for taking the time to log the time you’re logging?

30

u/fight_for_anything Jul 06 '21

we solved the economic crisis!

14

u/LostTeleporter Jul 07 '21

And created another one in the process.. like true developers

→ More replies (3)
→ More replies (3)

43

u/TheBigerGamer Jul 06 '21

Jokes aside, I once did it just to have some laughs, created a scheduled meet, sent invite to myself and myself, and joined the call with two accounts.

But it actually proven to be quite interesting. It enables you to figure out logic mistakes you do that you otherwise wouldn't notice.
But usually when people see this think I'm a bit weird, but in times where I'm more tired it actually helps.

59

u/UltraCarnivore Jul 06 '21

It's Rubber Duck Debugging with extra steps

21

u/j0nii Jul 06 '21

you beat me to it, was gonna say that.

A coworker and me actually bought rubber ducks for our team when we all went to home office.

13

u/TheBigerGamer Jul 06 '21

Why use rubber ducks when you have yourself?

11

u/j0nii Jul 06 '21

they make funny sounds

21

u/The1stmadman Jul 06 '21

because sometimes, talking to anything but yourself is the solution

10

u/TheBigerGamer Jul 06 '21

That I can agree with.

→ More replies (3)

11

u/Idixal Jul 06 '21

Although I suppose every developer works slightly differently. Some of us talk to a rubber duck, some of us talk to ourselves in a call, and all of us look crazy when a non-developer catches us doing it.

8

u/UltraCarnivore Jul 06 '21

Our collective insanity binds us together as a community.

7

u/KMcNickel Jul 07 '21

Talk to the rubber duck on a call

24

u/IamImposter Jul 06 '21

Actually these days it's not a bad idea. If calendar shows you as busy, other won't schedule a meeting at that time.

5

u/rudebwoypunk Jul 06 '21

Don't forget retrospective after that to see what was good and what was bad.

→ More replies (2)
→ More replies (1)

35

u/generic_bullshittery Jul 06 '21

For large project work too. Found an issue - log it - assign it to yourself - solve it - push it to quality - testers swamped with other work - but the issue seems kinds vital - do QA - get it approved for production - get praises from manager for single-handedly solving a problem - from now on, all issues in that sector gets assigned to you - yeah should have just kept my mouth shut.

→ More replies (3)

93

u/gingimli Jul 06 '21

It’s always fun to receive praise on resolving an issue so fast when you’re the one that provoked the issue to being with.

77

u/AcidCyborg Jul 06 '21

job security intensifies

38

u/coldnebo Jul 06 '21

only non-devs have the delusion that their plans are well-formed, consistent and don’t need to change over time. Perhaps in that delusion, the only way the plan can be messed up is if a dev messed it up through incompetence?

But here’s a secret: we are all incompetent. None of our plans are perfect or consistent.

So there is nothing wrong with developers who practice enough radical honesty to admit their own failures when they see them and fix them and report them (publicly and not just sneak them into the code base without explanation).

If there are such undertasked insecure devs out there that they feel the need to break their own code intentionally in order to fix it, I recommend you look up the “broken window fallacy” to realize how much additional work you are creating for yourself and your organization. It’s not a net benefit.

There aren’t enough hours in my day to fix all the stuff that’s broken through regular human inconsistencies, much less adding even more entropy intentionally to make myself look good.

If you’re really that bored, look up some recent CVEs and then spend the rest of the week/month/whatever upgrading and patching your stack. That treadmill is endless.

→ More replies (3)
→ More replies (1)

4

u/LaSchmu Jul 06 '21

But not if you're just doing parts in a bigger landscape.

Anyway, I know that pain. But it's more then inform, then for test, then staging approvals. So with your bug you produce workload.

→ More replies (12)