Transprogrammer

818 readers

1 users here now

A space for trans people who code

Matrix Space:

#transprog:socki.moe

Rules:

Don't be a meanie
- no *ism
- consider the feelings of somebody who might read what you say
Don't shitpost
Keep it wholesome
Must be trans / programming related

founded 1 year ago

MODERATORS

Xea@lemmy.blahaj.zone

When should I commit on projects? (pricefield.org)

submitted 1 year ago by skymtf@pricefield.org to c/transprogrammer@lemmy.blahaj.zone

11 comments fedilink hide all child comments

I am currently working on a small project, and I am working on getting it functional, but I question when exactly should I make commits. I usually just do it when I am done with working on it, but I know in practical projects often times commits are for one specific thing but given the project does not even work yet what exactly do I do.

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

[–] CameronDev@programming.dev 3 points 1 year ago

Hardware can fail randomly at any time. I would commit and push to a private repo as frequently as you can. You can always squash the commits later when it's complete. Definitely worth committing whenever you complete a feature, or before you remove any code (change of design, you may change your mind and want the code again).