Right, but in the context of making code changes, you can use diff. Which aligns with the Unix tool diff, and application of said diff with patch. So diff and patch are the operations that happen as you mutate a code base.
My comment is more about where it is headed. If you have been following Twitter you can read accounts of engineers pulling all-nighters, working over the weekend and “launching” the verification feature. Then, read accounts of users trying to use it but said feature not working. A few iterations of this for different features/products, and it will quickly impact his ability to ship anything (likely due to no automated testing in place, poor design decisions, etc.).
Meanwhile, all the takes on how Elon will have engineers shipping so many features is amusing. No sense of mounting tech debt and how that limits your ability to scale. Getting something quick out the door being your only objective. I don’t expect Elon to understand that dynamic, so he will just discover it the hard way when he is confused why all the sudden he can’t ship anything.
It isn’t. $AMZN accelerated capex in the last two years to meet the demand brought on by Covid. They even over built, but have also launched Buy With Prime to open up their logistical infrastructure as a service. It takes a long time to get where $AMZN is at.
At the end of the day, satisfying the customer is what matters. And customers are satisfied when their packages arrive quickly. $SHOP can’t compete with that because it has taken $AMZN two decades to build out the logistical infrastructure to support fast delivery times. And now with Buy With Prime program, sellers can use $AMZN logistics as a service.
Another direction is more automation. Cover more tasks by humans with robots (this union stuff acts as a selection pressure for innovation). Then just staff the place with qualified robot overlords.