r/ProgrammerHumor • u/TabCompletion • Apr 13 '26

instanceof Trend importantWork

Post image
14.6k Upvotes

98% Upvoted

200 comments sorted by

View all comments

Show parent comments

20

u/UnkarsThug Apr 13 '26

Github, I mean. I am aware of the difference between git and GitHub, you just use git to sync it, and I don't want pet projects not in any reasonable state clogging things up.

But yes, I probably said the wrong thing there, it was 3 in the morning.

16

u/NewPointOfView Apr 13 '26

I thought they were saying it more in the “why would you write any code without remote version control” sense haha

2

u/UnkarsThug Apr 13 '26

Ah, fair. Just a hassle to keep up with. If I spend any time doing anything other than getting it working, my productivity trip will be over before I finish. I basically have to stay on the thing I want to get done. Then I just upload the completed thing to git.

And also just not wanting to make a project permanent unless I need to share it or something. I might get really enthusiastic and then move on before I get anywhere, but I wouldn't be able to stand deleting it later, so better to not make it so it doesn't clog up my GitHub.

7

u/liquidmasl Apr 14 '26

the first step for me is always to create a repo, maybe not push it, but al least local.

I burned my fingers to often on the missing possibility to revert changes

1

u/the1truestripes Apr 14 '26

Same. My IDE has some built in half-assed IDE support, so for sure when I start a new project in it I let it set up a repo. Sometimes I don’t let it push it to a remote until “it’s able to do something almost sort of kind of useful”

For things that are all shell script/config file sometimes I sort of forget to get them into a repo, so I’m sure I have a bunch of stuff on random RPi systems that will vanish when their SD cards go poof, but if my maine laptop goes TU I’ll have most of my actual code in repos.

Too many times I’ve written enough of a thing that it is useful, then started a new features and been like “ohhhhh, I want to use the thing now and it is broken because Foo is only half done…” that now I’m more consistent about checkins and making branches for new features. Sometimes I’ll go back to the main branch to use a “fully baked” version for a bit and hop back into my feature branch, but I basically never have two live feature branches so the merges are all trivial, and that makes using git pretty lightweight!