3 ms·

Isnt this overloading git commits too much ? Like 50kb per commit message

• ibejoeb 8mo ago
  Git is totally fine keeping a few extra text files. These are ephemeral anyway. The working sessions just get squashed down and eliminated by the time I've got something worth saving anyway. At that point, I might keep a overview file around describing what the change does and how it was implemented. (I will give the agent boom a bit of credit: I write a lot more documentation now, because it's essentially instruction and initial instruction to anything else that works on it. That's a total inversion, and I think it's good.) The bigger problem is, like others have said, there's no one true flow. I use different agents for different things. I might summarize a lot of reasoning with a cheap model to create a design document, or use a higher reasoning model to sanity check a plan, whatever. It's a lot like programming in English. I don't want my tool to be prescriptive and imposing its technical restrictions on me. All of that aside: it's impossible that this tool raised $60 million. The problem with this post is that it's supposed to be a hype post about changing the game "entirely" but it doesn't give us a glimpse into whatever we're supposed to by hyped about.
  • ttoinou 8mo ago
    the git commits message description never go away though, unless you're editing the git with BFG cleaner
    • ibejoeb 8mo ago
      1. Commit messages go away if you remove the commit, but 2. Don't put it in the message. Put it in files.