Cthulhu: Organizing Go Code in a Scalable Repo (opens in new tab)

I think they have a similar goal. The difference sounds like gta uses git for change detection while bazel uses hashes to detect changes (hashes include the hashes of the transitive closure of the deps; it’s a dag). The latter is more robust in the face of noop edits that don’t change the output as well as distributed caching of test/build results.

It sort of "worked" for Lovecraft :-) even as people may suggest other actions and alternative interpretations of the human situation:

"H.P. Lovecraft Invented a Horrific World to Escape a Nihilistic Universe" https://newrepublic.com/article/119996/hp-lovecrafts-philoso...

oi

Once you realise that the reason you can't find the critical production code that's fritzing is because it's in another goddamn repo you didn't know about, you become a fan.

Having to reverse engineer CI/CD (or find someone who used to work on a project) to find where something came from is nuts. It should be as easy as search.

I find them appealing because orchestrating lots of git repos is such a mess.

Why? Because it doesn't follow the dogma of compartmentalizing everything for "maximum reusability"?

H̸̡̪̯ͨ͊̽̅̾̎Ȩ̬̩̾͛ͪ̈́̀́͘ C̷̙̲̝͖ͭ̏ͥͮ͟Oͮ͏̮̪̝͍M̲̖͊̒ͪͩͬ̚̚͜Ȇ̴̟̟͙̞ͩ͌͝S̨̥̫͎̭ͯ̿̔̀ͅ