← Back to context

Comment by tosti

10 hours ago

I also do this. Lots of weird commit messages because fuck that, I'm busy. Commits that are just there to put some stuff aside, things like that. I don't owe it to anyone to show how messy my kitchen is.

9 comments

tosti

Reply
Bootvis  10 hours ago

On the other hand, others don’t have to adopt, use or like your stuff which would be the reasons to publish it.

One big commit definitely doesn’t help with creating confidence in this project.

bitbasher  10 hours ago

> I don't owe it to anyone to show how messy my kitchen is.

There was once a time when sharing code had a social obligation.

This attitude you have isn't in the same spirit. GitHub (or any forge) was never meant to be a garbage dumping ground for whatever idea you cooked up at 3AM.

  • kstrauser  6 hours ago

    Never happened. My projects start with me goofing around and playing with things, accidentally committing my editor config or a logfile, etc. The first commit on my public release is a snapshot of the first working version, minus all the dumb typos and malcommits I made along the way.

    I don’t owe it to anyone to show how the sausage was made. Once it’s out the door and public, things are different. But before then? No one was the moral right to see all my mistakes leading up to the first release.

  • tosti  9 hours ago

    It requires self-discipline to stay organized. A vcs is just a tool. I'm never organized, my brain just works that way. Whatever the tool, I'll create a mess with it. So as long as the project structure and its code is all good I can't care about anything else.

  • greenavocado  9 hours ago

    Explain why you think making a single commit is related to any source code sharing obligation? You completely failed to establish why making a single commit is indicative of it being garbage. Your statements are a series of non-sequiturs so far and thus I can't take you seriously.

    • bitbasher  9 hours ago

      > Explain why you think making a single commit is related to any source code sharing obligation?

      When you share code it's presumably for people to use. It is often useful to have commit history to establish a few things (trust in the author, see their thought process, debug issues, figure out how to use things, etc).

      > You completely failed to establish why making a single commit is indicative of it being garbage.

      A single commit doesn't mean it's garbage. It erodes trust in the author and the project. It makes it hard for me to use the code, which is presumably why you share code.

      My garbage code response was in regards to the growing trend to code (usually with ai) some idea, slap an initial commit on it and throw it on GitHub (like using a napkin and tossing it in the rubbish bin).

      1 reply →