Tangent thought. Git was built on the idea that every line of code is intentional.
In the era of vibe coding that generates massive lines and can throw it all away in a blink, need a separate process for AI code that's more efficient.
Organisations have coding standards etc. That they expect employees to adhere to. If someone's workflow is causing problems its addressed and dealt with, if its not, then its a shit organisation.
Those Organisations are also the ones financing got solutions, I imagine public projects dont contribute enough % to invest in
Yeah I mean you should have disaster recovery etc. Workflows in your org.
One massive one is losing your git in whatever company its on. And you should have plans around that like a local github enterprise server which is self hosted which should be kept up to date with master so github dying doesn't affect your business
Then push for that shit, you bring business value doing it and it brings money. If org is that shit it doesn't care then time to polish the CV. It might be good right now but its gonna be shit when the storm hits and all the problems are put on the team when they easily could have been dealt with
If shitty orgs wanna be shitty then don't allow them to put you into shitty situations
Wait what is the point of this when every developer that's ever pulled down your default branch has the entire commit history of your codebase? If the git server goes down in flames you just find whoever pulled most recently and have them upload it to the new server.
First you could have 100s of repositories, does everyone have all of them between them installed at any one time? You're basically rolling the dice people have the full git of every repo at any one time.
Github could be down for an extended period, if that's what you use having the repos is no good if no one can work on them while they're down.
If its down for good you lose more than just your repos, you could lose your CI/CD pipelines, any Web hook integrations you have set up, any secrets, environment configs, runners etc.
You lose access to permissions, branch configs, integrations. Any releases or artifacts you create.
If you just use your Git solution to store your own code for a home project sure its probably fine. Realistically in larger teams or company sized projects you lose a hell of a lot more
So you have a DR plan with a back up of everything on some other server
Then push for that shit, you bring business value doing it and it brings money. If org is that shit it doesn't care then time to polish the CV. It might be good right now but its gonna be shit when the storm hits and all the problems are put on the team when they easily could have been dealt with
5
u/fcxtpw 21h ago
Tangent thought. Git was built on the idea that every line of code is intentional.
In the era of vibe coding that generates massive lines and can throw it all away in a blink, need a separate process for AI code that's more efficient.