Git

The word branch sounds technical, but the idea behind it is simple.

A repository is your project folder with its whole history saved by Git.

That means every version of every file, going all the way back to the first day, and a branch is a copy of that project you can change without touching the real one.

Nothing gets locked and nothing gets deleted when you create a branch.

Main and master mean the same thing.

And the switch from one name to the other was a naming choice, not a new feature you have to learn.

Branches in Git are also cheap, and that's the part people coming from older tools find hardest to believe.

In the systems that came before Git, making a branch was a slow, heavy operation you did rarely and carefully.

Like the part about coding that I hated was like the... semicolon oh the indentation was wrong and stuff like that like that is what exhausted me like way back early in my career which is why i ended up choosing like a a product path instead of an engineering path like way back in the day but now we're back to the point where like i i literally like even to like i even find it just easier like split up an agent i'll be like cool clone the repo because like i don't even want to think about what the you know the get Command line is to clone it in the right way and the right depth and stuff like that.

And so I think those are like a small example for me that like I don't want to think about Git commands anymore.

Yeah, 100% like doing things like go clean up the commits on this branch or rebase and resolve the commands.

Yeah, like...

So I made a bunch of little demos like, um, uh, on my website, I've shared two prototypes.

One was a document x-ray.

which was like, take Mark Zuckerberg Senate testimony, the GitHub's terms of use and the Apollo moon landing radio transcript, and basically use Jeff to figure out the meaning of certain sense of all the sentences and kind of allow you to like x ray and view it.

Like, for example, in the Zuckerberg testimony, it's funny, it's like, you know, does not answer the question.

I don't want to be in the weeds for everything.

And in fact, when you hear, you know, Anthropic's numbers of, Anthropic rewrote, they rewrote Git.

And I think it's called Scion.

They released something.

Oh,

they made their own Git, yeah.

Right.

To make it more efficient for Anthropic's internal use.

I think the move to make is focus on who owns the customer desktop, right? If you're in financial services, it's the Bloomberg terminal.

If you were coding five years ago, it was Git.

That's why Microsoft bought Git.

If your recruiter was LinkedIn, Microsoft bought that.

It used to be Stack Overflow like eight years ago, maybe even five years ago, right? Now the desktop is changing and it's changing away from Anthropic and away from OpenAI.

Conductor è l'orchestrazione visiva di agenti software su macOS.

Un approccio pionieristico alla programmazione agentica trasforma lo sviluppo distribuito automatizzando rami Git e unione di codice complesso in tempo reale.

Il paradigma del wave coding e l'automazione multi-agente.

L'evoluzione dell'ingegneria del software sta compiendo un salto di qualità con il passaggio dal completamento contestuale del codice alla delega autonoma di intere funzionalità.

Isolamento tramite work tree e parallelizzazione dei task.

Uno dei maggiori limiti dell'automazione software risiede nel rischio di corruzione del repository durante refactoring invasivi.

Conductor supera questo ostacolo sfruttando i work tree di Git.

Per ogni agente operativo viene creata istantaneamente una directory di lavoro indipendente collegata a un ramo secondario isolato.

I think even just in the last year, I've seen the way software engineers work, and I'm looking a little bit from the outside because I'm not an engineer.

I've seen changes in the way software engineering works to the transition to the cloud and of Git and version control tools that we all use today.

I've seen changes in how software engineers work with each other.

I've seen changes in how PRs get reviewed and how feedback gets given.

At this point, also,

you should probably learn how to use Git or something.

yeah i guess it just gets like underneath maybe hopefully i don't know if that's the functionality

if you assume it does something that i think should be known uh if you are like a mod developer or a hack developer and you can put that on your resume right you could be like oh i did this and that gives you some computer science credentials right hopefully as far as i know it right um and learning how to use git and github for your projects in this case gives you extra stuff because or like you know git lab or one of the other things it gives you extra it gives you extra credits because that's actually used in the industry right you guys know what i'm talking about

No way, dude.

As if we had a fucking utility for that.

Anyway, your pack is a Git repository you can push to GitHub or GitLab.

Every change is a command that can be found, pulled by collaborators and reverted.

And his whole thought is he's like, you need to have a source of truth that is largely dynamic.

And it needs to be about like, what is the best decision making I can do in this moment at this time? And it doesn't matter if Figma and Git are conflicting with each other.

Because if Figma says the primary color is red and the Git repository says the primary color is blue, who's right is a matter of opinion in that moment.

Maybe red is the right color because it's accessible in this moment.

Maybe blue is the right color because it's actually what's on brand.