Skip to content
DevMeme
6156 of 7590
Git Typo Workflows: Reactive vs. Proactive Solutions
VersionControl Post #6751 · source on Telegram

Git Typo Workflows: Reactive vs. Proactive Solutions

Description

This is a two-panel 'Wojak vs. Chad' meme comparing two different developer approaches to a common problem. On the left, the 'Soyjak' or 'Wojak' character, depicted with a smiling mask hiding a crying face, is shown above the text 'GIT PUHS' followed by 'GIT PUSH'. This represents a developer who frequently makes a typo and must manually correct it each time, hiding their frustration. On the right, the stoic, bearded 'Chad' character is shown. Below him, the sequence of commands is: 'GIT PUHS', 'GIT CONFIG --GLOBAL ALIAS.PUHS PUSH', and then 'GIT PUHS' again. This illustrates a superior workflow: upon making the typo, the Chad developer immediately creates a global Git alias, so the typo 'puhs' will forever work as 'push'. The meme humorously contrasts the inefficient, repetitive cycle of a junior or less savvy developer with the proactive, problem-solving mindset of a senior engineer who invests a small amount of time to create a permanent, automated solution

Categories

VersionControl CLI DeveloperExperience DX Tooling Automation

Common Tags

Git DeveloperHumor GitCommands VersionControl CLI CommandLineInterface CLITools DeveloperShortcuts DeveloperErgonomics ToolingFrustration CodingMistakes

Comments

24
Anonymous ★ Top Pick The junior developer spends 5 seconds fixing the 'git puhs' typo every time. The senior spends 5 minutes creating the alias so they never have to think about it again. The principal writes a pre-commit hook to block any future typos from reaching the team's shell history
  1. Anonymous ★ Top Pick

    The junior developer spends 5 seconds fixing the 'git puhs' typo every time. The senior spends 5 minutes creating the alias so they never have to think about it again. The principal writes a pre-commit hook to block any future typos from reaching the team's shell history

  2. Anonymous

    Real seniority is when you optimize Git for your fingers’ entropy budget instead of refactoring your neural net

  3. Anonymous

    The real senior move isn't creating an alias for 'puhs' - it's having already aliased 'yolo' to 'git add . && git commit -m "WIP" && git push --force' for those Friday afternoon deployments

  4. Anonymous

    The real senior move is creating a git alias for your typo instead of learning to type correctly - because why fix your muscle memory when you can just configure your way around it? Bonus points if your .gitconfig has more aliases than actual commits, and you've aliased 'git status' to 's' but still type 'git st' out of habit from your SVN days

  5. Anonymous

    True senior move: stop retraining your thumbs and make the interface adapt - git config --global alias.puhs push is SRE-grade toil reduction for keystrokes

  6. Anonymous

    Senior move: codify muscle memory with `git config --global alias.puhs push` - until you’re on a vanilla jump box and “puhs” ships nothing but embarrassment

  7. Anonymous

    Senior dev flex: aliasing 'push' to 'push' for that enterprise-grade config indirection and zero keystroke savings

  8. @gegechin 1y

    https://guthib.com/

  9. @OKomarov 1y

    git config --global alias.🔥 commit -am "fixed 💩" reminds me of the time I forked Python to accept emojis as variables

    1. @sysoevyarik 1y

      Python if it was good

    2. @itsTyrion 1y

      git config --global alias.YOLO1 commit -am "fixed 💩" git config --global alias.YOLO2 push -f origin master

  10. @mrYakov 1y

    git puhs fuck //real command btw

    1. @Vlasoov 1y

      git reabse fuck

  11. @SamsonovAnton 1y

    Git Poohs

    1. @phoetik 1y

      Why they look mutable

      1. @SamsonovAnton 1y

        Because they do hardcore asm, not functional programming!

  12. @pyrothefuck 1y

    there is a cli tool called thefuck

  13. @LapkiProch 1y

    пше

  14. @yanisalwayslies 1y

    gaa; gcmsg 'feat: nothing'; gp

    1. @NaNmber 1y

      you can't commit without message anyway, so gcmsg seems excessive

      1. @yanisalwayslies 1y

        yeah but i provided the message

        1. @NaNmber 1y

          I mean the short command itself, gc would be sufficient

  15. @qwnick 1y

    why do you need to push 2 times?

    1. dev_meme 1y

      Twice in a lifetime?

More like this

More like this in VersionControl →
VersionControl Git DeveloperHumor
The Reviewer Wears the Full Test Suite

The Reviewer Wears the Full Test Suite

CodeReviews
Removing Claude From the Commit

Removing Claude From the Commit

AI ML
Self-Host GitHub? Impossible to Match That 89% Uptime

Self-Host GitHub? Impossible to Match That 89% Uptime

VersionControl
Use J and K for navigation