769

Manager: This task only takes 30 minutes. Why did it take you the whole day? (programming.dev)

submitted 11 months ago by hypnotic_nerd@programming.dev to c/programmer_humor@programming.dev

95 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] Anticorp@lemmy.ml 40 points 11 months ago

There's a bigger issue than your commit message if you don't even know what you just coded and are committing.

[-] AVincentInSpace@pawb.social 25 points 11 months ago* (last edited 11 months ago)

You see, sometimes I code something, go to bed before finishing it, come back, decide not to commit because then I'd have to think of a commit message and I just want to code, start working on an unrelated feature, do that for a couple days, get distracted by life stuff and put the project down for a few weeks/months, rinse and repeat, and then I finally get around to writing a commit message because I'm about to start a huge change and I want a restore point and I'm like. Okay, it's been like 3 months since my last commit, I'm pretty sure my code can now do something it couldn't 3 months ago but come on, I can't even remember what I had for lunch last Thursday

I'm well aware this is terrible practice but I don't know how to stop doing it

[-] dukk@programming.dev 20 points 11 months ago

Commit more often. Maybe work in a different feature branch, and don’t be afraid to commit your half-working crappy code. If it’s a personal project/fork, it’s totally acceptable to commit often with bad commit names and small unfinished changes: you can always amend/squash the commits later. That’s how I tend to work: create a new branch, work on the feature, rebase and merge (fast forward, no merge commit). Also, maybe don’t jump around working on random features :P

[-] ExtraMedicated@lemmy.world 11 points 11 months ago

Jumping around to random features is how my ADHD brain works most efficiently.

[-] Slotos@feddit.nl 5 points 11 months ago

Good news, TDD is methylphenidate of software development!

[-] AVincentInSpace@pawb.social 4 points 11 months ago* (last edited 11 months ago)

but...but new feature shiny

Fr tho this is all excellent advice

[-] Anticorp@lemmy.ml 3 points 11 months ago

You can help yourself a lot here by making commits every time you make a meaningful change. A feature doesn't need to be complete to commit major checkpoints along the path to completion. That's what feature branches are for. Commit often. It'll help you think of messages, and it'll help you recover in the case of catastrophe.

[-] adrian783@lemmy.world 1 points 11 months ago

you can setup a on-save script to force you to commit when the number of changes is greater than a certain number from the previous commit.

[-] akkajdh999@programming.dev 13 points 11 months ago

I just get too excited about actually implementing/fixing something (random things that I see along the way) more than commit ceremony (nobody will care about it in my project anyway other than one random guy who gave the repo a star)