lobsters score: 2 · tags: vcs
Yeah, if you have 100 tiny little repositories, someone(s) in the organization is running around keeping everything synchronized across them. If you aren’t the one paying that tax, it probably works great. If you are the one doing the work, or you watch the person(s) frantically doing all the work, then you’ll start to realize how high the tax is.
score 1 · canonical
Back when I was working at EA, the company went through a wave of organizing code into packages that could be shared by multiple game teams. This was generally a great thing and reduced the insane amount of NIH that existed before then.
However, every game team had its own Perforce repository, and there was no real mechanism or policy in place to update those packages. It was all just ad hoc whenever some random game team needed a fix from someone else’s version of a package, they would take it.
One of the last things I did before leaving EA was spend 9 months of my life doing nothing but migrating packages from one repo to another and getting teams on the latest version of stuff. I’m not saying that’s why I left EA. There were plenty of reasons. But it was definitely one of them.
score 1 · canonical
Hey, love your book. Yours, along with Thorsten’s monkey language books, really demystified programming language design for me. I still need to take a run at building a Hindley–Milner type system for the language I have brewing in my head.
score 3 · canonical