I wonder if they'll continue to support and develop Cog [0], which I've found quite useful for local deployments of models (as well as to Replicate's servers).
Not at all snarky because I have no idea what the real answer is here, but although this sounds pretty good, it strikes me how in conflict this would be with most peoples' ideals if we tried any sort of system to scale this to larger populations (like a city).
Perhaps we want privacy-but-not-anonymity. Or perhaps society doesn't scale easily.
> And you'd better believe wherever they buried the lines they'd have objections and expensive consultations about the disruption and the HoUsE VaLuEs caused by trenching, drilling and service structures.
But those are temporary disruptions. Overground lines are permanent.
The reason utilities and the Grid prefers overground is: it's cheaper. It's not better. It's cheaper.
Something I've seen discussed very little is that Claude Code can be opened in a directory tree of any type of document you like (reports, spreadsheets, designs, papers, research, ...) and you can play around in all sorts of ways. Anthropic themselves hint at this by saying their whole organisation uses it, but the `Code` moniker is probably limiting adoption. They could release a generalised agent with a friendlier UI tomorrow and get much wider workplace adoption.
What this shows to me, as someone who has committed some of the unholy crimes above, is that people want their system, however esoteric, to come naturally to them.
I think reading docs, understanding a new system which someone else has designed, and fitting one's brain into _their_ organisational structure is the hard part. Harder than designing one's own system. It's the reason many don't stick with an off-the-shelf app. Including Org mode.
The same has happened in the United Kingdom wrt deer and predators including wolves (which are locally extinct) -- a blunt instrument because we can think of no other way of protecting livestock. The result is we "have to" regularly cull thousands of animals instead of letting an ecosystem manage itself.
Preventable via multiple methods, you've been downvoted presumably for seeming insensitivity, but it seems a valid question. Water is plentiful, it's a rich area. This stuff can be prevented. Why wasn't it?
Anecdotally, as a developer I really appreciate a well-thought-out monorepo. All the code is there. You don't have to dig around anything legacy or outdated. Searching is a breeze and it's _fast_. Updating both simple and complex logic is equally easy. You don't need to somehow discover that some other repo uses the thing you changed. Everything has the same deployment process. The tests test the thing, as soon as you push it - instead of months down the line, when someone finds forgotten repo again and oh, it's never been tested with the new functionality in our main repos. Dependency hell doesn't really exist.
There seems to be more discipline around monorepos because they're collectively owned, whereas many repos across an org each become someone's baby, and practices diverge until teams in the _same company_ fork each others' repos because they don't get along.
- http://apopo.org/support-us/apopo-visitor-center/