639
Always commit (lemmy.world)
top 19 comments
sorted by: hot top controversial new old
[-] chickenf622@sh.itjust.works 90 points 1 year ago

He doesn't want to push at such a late hour. Give him a break.

[-] superduperenigma@lemmy.world 39 points 1 year ago

Gotta have something to say in stand-up the next morning, otherwise your PM will assign you another task.

[-] eestileib@sh.itjust.works 35 points 1 year ago

How many times did I push at 2am so I could go home, get to the freeway entrance, realized I fucked something up, sighed, and turned around to go back and fix it...

(This was like 1999, we didn't have access to Perforce from home).

After a year or so I realized I should just develop the willpower to check it in after sleeping on it.

[-] jaybone@lemmy.world 7 points 1 year ago
[-] eestileib@sh.itjust.works 2 points 1 year ago

"P4 server's down."

"Sports Page, or Tied House?"

[-] yiliu@informis.land 67 points 1 year ago

"No, wait, it's not what you think! There's a continuous integration system, a commit would've triggered a new build! It might have paged the oncall! Babe! The test suite has been flaky lately!"

[-] Cqrd@lemmy.dbzer0.com 61 points 1 year ago

Dude just stopped before he got to a logical stopping point where it would make sense to commit and push

[-] GigglyBobble@kbin.social 48 points 1 year ago* (last edited 1 year ago)

That's actually not that rare when I work later than usual. Some stupid problem my brain is too fried to solve. Eventually I give up, feeling defeat for the whole evening and solve the problem in 10 mins the next morning. Get enough sleep, people.

[-] sunbeam60@lemmy.one 25 points 1 year ago

However, much research shows the hand banging against the wall period is required for you to achieve the morning breakthrough.

The sleeping break is where your neurons form new connections based their activity yesterday. The “thinking hard” and the frustration is a required part of the morning epiphany.

God I love programming.

[-] GigglyBobble@kbin.social 4 points 1 year ago

Thanks. I did not need to know that. Oh well, off to more headbanging then.

[-] min_fapper@iusearchlinux.fyi 42 points 1 year ago

The most common advice for git is

commit early. commit often

Do not however, follow the same advice for relationships.

[-] ______@lemm.ee 35 points 1 year ago

I worked today and have O commits.

[-] cupcakezealot 20 points 1 year ago

never commit on friday afternoon because you'll regret it on monday morning

[-] gitstash@lemmy.world 19 points 1 year ago

git stash, girl

[-] Anticorp@lemmy.ml 11 points 1 year ago

ABC, always be committing.

[-] XTornado@lemmy.ml 10 points 1 year ago* (last edited 1 year ago)

W E

W A S

[-] HubertManne@kbin.social 5 points 1 year ago

commit history was how I determined when to do the nightly and big weekend backups for a place I admined at one point. It was so annoying that we had one developer that liked to stay up way late and one that like to get up way the fuck early. Thank god they were all colocated at that point in time. If they had different timezones I would have just had to say eff it and let them have some poorer preformance.

[-] atticus88th@lemmy.world 4 points 1 year ago

Honey, I was reviewing the new interns pull request. She was having a real hard time. We kept pushing and pulling until we eventually found ourselves getting that commit all over the codebase. Needless to say it won't happen again, it was a one night standing review.

[-] StarkillerX42@lemmy.ml 3 points 1 year ago

No babe! I was busy doing review!

this post was submitted on 15 Sep 2023
639 points (100.0% liked)

Programmer Humor

19187 readers
1035 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS