Every time I commit I have to look through git diff, figure out what the hell I actually did, come up with something intelligent to say about jt, possibly split the commit into multiple commits if I changed multiple things, do some shuffling with git reset and git add…
For some reason all my personal projects are all like 4K SLoC with 50 total commits, all of which include apologies for not doing more smaller commits
Patch add - it shows you particular changes you made, and you choose whether or not to include them in the commit. (You can then use git stash -k to stash only the changes you did not add, so you can test before you commit.)
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
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
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.
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)
I spend much time splitting them up inside visual studio by file and individual lines changed to try and separate my many simultaneous changes into several somewhat usable commits. If I was stupid enough to make some big refactor at the same time I might just have to throw in the towel… It’s really painful after a few weeks to try and pick up the pieces of what I was doing but never commited too lol.
Just comment out the window until it is fixed. Either way it isn’t dangerous as long as you surround it with try/catch.
But I don’t know exactly about that catch part if something happens a few miles above.
I was chatting with a friend, and she mentioned how she tries to at least set up a README, which includes her vision for the project and her plan for the implementation, design, and goals.
Best case scenario is that the planning helps her complete the project herself. Worst case scenario, someone else can pick up where she left off and use her considerations for the project.
I’m thinking of doing that for future projects too
A Free Software License is even more important. There are many great projects out there which you can’t modify etc. because the project isn’t distributed with a license (which means “all rights reserved” in most jurisdictions).
I have my repos on Codeberg and one of the ‘disadvantages’ is that, well, it’s a non-profit, so I genuinely don’t want to waste their resources.
They ask you to only host open-source repos there, meaning that using it for backups of shitty personal projects, even if I would throw in an open-source license, is just out of the question for me.
And that has weirdly been a blessing in disguise. Like, if it’s not useful for humanity to see, do I really care to keep it around forever?
And I’ve had three projects now where I felt an obligation to push them over the finish line of actually making them a useful open-source project. Which had me iron out some of the usability shortcuts I took, made me learn a good amount of code quality stuff and of course, just feels good to complete.
Well, Codeberg is a non-profit. I would say if it’s just a few kilobytes/megabytes of code, upload it and donate $10. That should be enough to store that for decades.
I sometimes look for small stuff. Boilerplate code, how other people configure stuff that isn’t well documented, niche interest stuff even if it’s not finished. Sometimes stuff like that is useful.
That’s why I host all my shitty unfinished projects in a Gitea instance in my VPS. Now they actively cost me money and I feel (a tiny bit) more incentivized to do so something with them!
Come they told me, pa rum pum pum pum A new born King to see, pa rum pum pum pum Our finest gifts we bring, pa rum pum pum pum To lay before the King, pa rum pum pum pum, rum pum pum pum, rum pum pum pum,
So to honor Him, pa rum pum pum pum, When we come.
Little Bobby, pa rum pum pum pum I am a poor boy too, pa rum pum pum pum I have no gift to bring, pa rum pum pum pum That’s fit to give the King, pa rum pum pum pum, rum pum pum pum, rum pum pum pum,
Shall I play for you, pa rum pum pum pum, On my unsanitized database inputs?
programmer_humor
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.