• 2 Posts
  • 130 Comments
Joined 2 years ago
cake
Cake day: July 30th, 2023

help-circle










  • It doesn’t matter what it stands for. That’s not how acronyms work.

    You don’t say “yolwa” for “YOLO”
    You don’t say “Ah-ih-dees” for “AIDS”
    You don’t say “britches” for “BRICS”
    You don’t say “sue-knee” for “CUNY” (City University of New York) Etc.

    And if you want to argue specifically about G:
    You don’t say “Jad” for “GAD” (generalized anxiety disorder)
    You don’t say “joes” for “GOES” (Geostationary Operational Environmental Satellite)

    It’s not a hill I’m going to die on, I use both pronunciations, but the only argument I’ve ever believed for the proper one is that the creator pronounced it “jif”. https://en.m.wikipedia.org/wiki/GIF#Pronunciation

    Now let’s talk about “gibs” you heathens.









  • Not git, Perforce, but I used to have a guy on my team that would do weeks of work without checking in. 1000s of lines in 10s of files.

    I gave him shit for every code review, every time we had 1-on-1s, and while he was doing his tasks. Nothing got through to him.

    So I just kept dragging him back on check-ins. I’d nitpick the shit out of every line (and normally I hated that.) His stuff would inevitably break the build or be full of bugs anyway (duh) so I never felt bad that I was holding back his career since he was never getting things done “on time.”

    If you can’t/won’t break your work down into smaller chunks you aren’t a skilled programmer and/or don’t have respect for the people you work with who have to review your shit.