Skip to content
DevMeme
6488 of 7590
Goku Demonstrates the Cautious Approach to Copy-Paste Operations
DeveloperProductivity Post #7113 · source on Telegram

Goku Demonstrates the Cautious Approach to Copy-Paste Operations

Description

A two-panel Dragon Ball Z meme with the header 'It doesn't hurt to be cautious'. Top panel shows Goku in a focused prayer-like pose with text 'CTRL+C CTRL+V' representing a normal copy-paste. Bottom panel shows Goku looking more intense with a knowing finger raised, alongside text 'CTRL+C+C+C+C+C CTRL+V' representing the paranoid habit of pressing Ctrl+C multiple times to make absolutely sure something is copied before pasting. This captures the universal developer anxiety of not trusting the clipboard

Categories

DeveloperProductivity IDEs Editors DeveloperExperience DX

Common Tags

KeyboardShortcuts CopyPasteProgramming DeveloperHumor CodingHumor DeveloperPsychology AnimeReference RelatableHumor DeveloperMindset TrustIssuesInTech DeveloperProductivity

Comments

75
Anonymous ★ Top Pick The clipboard has a 100% success rate on Ctrl+C, but my trust issues from that one time it didn't paste correctly have a TTL of infinity
  1. Anonymous ★ Top Pick

    The clipboard has a 100% success rate on Ctrl+C, but my trust issues from that one time it didn't paste correctly have a TTL of infinity

  2. Anonymous

    I don't just hit CTRL+C multiple times; I'm sending a packet burst to the clipboard manager to establish a quorum and ensure data replication before the paste commit

  3. Anonymous

    If only our eventual-consistency databases synchronized as faithfully as we hammer CTRL+C before every remote ‘ssh’ paste

  4. Anonymous

    After 20 years in the industry, I still don't trust the clipboard API more than I trust a junior's 'minor refactor' on a Friday afternoon - at least with the refactor, git blame tells me who to haunt

  5. Anonymous

    After 20 years in the industry, I've learned that pressing CTRL+C five times doesn't actually make the clipboard more reliable - but I still do it anyway, because the one time I didn't, I lost a perfectly crafted regex that took me 45 minutes to write. It's not paranoia if the clipboard has actually betrayed you before

  6. Anonymous

    Years of prod shells teach you to treat paste like a two-phase commit - spam SIGINT until the prompt is consistent, then apply

  7. Anonymous

    My clipboard uses at-least-once delivery - mash CTRL+C until quorum, then paste; just don’t run leader election in a prod shell where SIGINT is exactly-once

  8. Anonymous

    Triple CTRL+C: because clipboards suffer eventual consistency too

  9. @Valithor 11mo

    Am I the only one who has noticed that control C just sometimes straight up doesn't fucking work

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      Yes since fucking Clipboard history in build 18XXX was added

      1. @Valithor 11mo

        That can be disabled though, and I still run into this issue on an embedded version of Windows where the clipboard history is disabled

        1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

          Yea but it probably had some internal change in the clipboard pipeline and its got ruined for all

      2. @Broken_Cloud_1 11mo

        No one mentions the chaotic Linux clipboard

        1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

          Oh no, tell us now I am curious

          1. @Broken_Cloud_1 11mo

            It just sucks

            1. @RiedleroD 11mo

              works for me

              1. @RiedleroD 11mo

                I should get a clipboard manager at some point tho 🤔

              2. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

                You are evil

                1. @RiedleroD 11mo

                  meow?

                  1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

                    "Works on my machine" from a random spectator is literally the worst thing you could have done 😂

                    1. @RiedleroD 11mo

                      what can I say. perhaps their unreliable clipboard is a skill issue

    2. dev_meme 11mo

      Same was happening with me since at least El Capitan on MacOS

      1. @Algoinde 11mo

        That's because you're supposed to press Command + C, you silly.

  10. @Valithor 11mo

    Like I don't know if it's specifically a thing that has started since Windows 10, but there is definitely some weird shit going on with trying to copy stuff sometimes

    1. @dukefox11 11mo

      it's the windows clipboard, appeared in win 10. Google will know more

    2. @SamsonovAnton 11mo

      I faced similar issue while using Firefox in Windows 7 several years ago: in some circumstances at least the keyboard shortcut for copying didn't work (don't remember whether the menu item worked either). Perhaps that was just a big that was fixed several major releases later, as I don't remember facing it recentrly (and I still use Windows 7 btw 🤓).

  11. @Algoinde 11mo

    This is genuinely a learned behaviour if you think about it I think the main reason is the fact that a) we know the action is repeatable without consequences b) there is no visual indication that something was succesfully copied c) sometimes copying actually doesn't copy for reasons unknown (focus? dropping inputs?)

    1. @Algoinde 11mo

      Like, some developer's shit code actually made us distrust the shortcut until the end of time, and it may only have been a single case of it not working in a specific program

  12. @dukefox11 11mo

    As we say in Russia: "copy seven times, paste once"

  13. @Algoinde 11mo

    I've just never thought about why I actually mashed ctrl+c before now

  14. @Valithor 11mo

    Because Windows 10 has gaslit us into thinking we must have fucked up pressing the hotkey for pasting to fail

  15. @cold_is_the_void 11mo

    "+yy "+p

  16. @Valithor 11mo

    I can only assume it's poorly or improperly implemented

  17. @Valithor 11mo

    Exactly

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      There is 2 clipboards since Windows 8. Literally there is one for WinRT and for Win32

  18. @Valithor 11mo

    Hmm... I don't remember what version I have to use for work. Guess I'm checking that in 5 hours.

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      And I think when they implemented the online syncing and history it got fucked because now the plain win32 clipboard also has async pipeline

  19. @Valithor 11mo

    Oh it's definitely the async pipeline

  20. @Valithor 11mo

    From what I figured is you go to copy, it takes an unknown number of ticks before it will actually hit the clipboard, and if you try to paste before it finishes then it just never hits the clipboard because the async will fail

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      Yeah 100%

  21. @Valithor 11mo

    Makes no sense to me why there's a race condition there

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      Because there is 2 clipboards that have to get syncronized and there is the online clipboard thing too

  22. @Valithor 11mo

    Windows internal API bullshit at work again

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      Win32 Clipboard api is not async btw

    2. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      Fr

    3. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      And then there is the old mail app that is winrt and clears the clipboard if it wrote to it and you close it. "Security"

  23. @Valithor 11mo

    I don't think most things were back then

  24. @Valithor 11mo

    This issue all started when they started trying to implement react into the operating system FOR SOME GOD FORSAKEN REASON

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      This is actually unrelated

  25. @Valithor 11mo

    Probably, it's just the timing of it all is roughly the same

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      Yeah true, I know WinRT with sync on its own works well because I used WinRT only Windows before and it worked reliably as fuck but on desktop windows where 90% of apps you use is win32 doesn’t work is ridiculous

      1. @Valithor 11mo

        By the way, totally unrelated, but fuck yeah NGNL

  26. @Valithor 11mo

    Probably just a compatibility layer thing then. Windows 12/13 will maybe save us?

    1. @Valithor 11mo

      I said this before I gave it enough thought and remembered that they're trying to push windows as a service, so... They need to get their API versioning shit together, and I have no evidence to believe they have even started attempting to do that

      1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

        They did this with uwp/winrt but nobody liked to develop for that api

    2. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      The thing is Microsoft tries to replace win32 by winrt so win32 is the compatibility layer now 💀

  27. @Valithor 11mo

    Kind of figured the whole reason they would deprecate an API like that is because they would remove it in a future release. I don't know why we still have this ancient architecture floating around programs that are clearly breaking on the new versions.

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      Because people dont like change and developers are lazy to learn how AppContainers work

  28. @Valithor 11mo

    They're so afraid of making breaking changes that it's detrimental to the end user. If anything they should adopt versioned APIs instead of a single unified one with multiple layers of compatibility gumming it all up.

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      Yes winrt has that

    2. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      Look up onecore api set

  29. @Valithor 11mo

    This happens with literally every single thing Microsoft touches though. I lost track how many instances of "new" and "old" outlook and teams programs they pushed, or O365 shenanigans

  30. @KratzKatz 11mo

    I noticed ctrl+c not working too. Just like the print screen key, unless i click the task bar first

  31. @Valithor 11mo

    Since we're talking about it, I think this whole issue came from efforts to get rid of the white (hung) application windows that happened since at least XP when an application is thought to not be responding by the operating system. It used to be that applications would act like they're not responding while they're still loading If you try to interact with them too quickly during that process, it would cause it to hitch and interrupt (and push that interrupt to the end of the priority stack) until the CPU would eventually try and go back to it later.

    1. @Diotost 11mo

      They were not white untill Windows Vista or 7

      1. @Valithor 11mo

        Vista, that was it

  32. @Valithor 11mo

    I swear to God if I could just have a few months at Microsoft...

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

      We literally need windows 10 X

      1. @ZgGPuo8dZef58K6hxxGVj3Z2 11mo

        Win32 apps run in a VM like on Xbox

  33. @Valithor 11mo

    Because nobody uses Linux

    1. @Broken_Cloud_1 11mo

      😆

  34. @Valithor 11mo

    The vocal minority can boo me all they want but I'm still right

  35. @IPDan4ik 11mo

    just using y to yank with text highlighting (neovim btw)

  36. @zzzFagon 11mo

    So many comments on this issue yet no one has found a solution. Very repeatable in Excel for me

  37. @PermanentDaylight 11mo

    I do ctrl + x, ctrl + z, ctrl + v

More like this

More like this in DeveloperProductivity →
DeveloperProductivity KeyboardShortcuts CopyPasteProgramming
Blaming Productivity on Missing Ergonomic Keyboard Instead of Focus

Blaming Productivity on Missing Ergonomic Keyboard Instead of Focus

DeveloperProductivity
Drake Meme: Opening Project Just To Hit Ctrl+S Instead Of Coding

Drake Meme: Opening Project Just To Hit Ctrl+S Instead Of Coding

IDEs Editors
The Developer's Compulsive Save Reflex

The Developer's Compulsive Save Reflex

DeveloperProductivity
Use J and K for navigation