breischl
Joined 14 years ago
Joined 14 years ago
I think the same thing about a lot of code, too. Sometimes you really are just hammering out boilerplate. But a lot of times even writing test code is a great opportunity to realize the main code could be improved. But the LLM probably won't tell you that.
> Roman-era mining activities increased atmospheric lead concentrations by at least a factor of 10, polluting air over Europe more heavily and for longer than previously thought, according to a new analysis of ice cores taken from glaciers on France's Mont Blanc.
A lot less than modern technology manages, but a lot more than nothing. And that with a much smaller population.
https://phys.org/news/2019-05-roman-polluted-european-air-he... https://en.wikipedia.org/wiki/Ruina_montium
Do you also wonder how we'll get rid of used coal power plants, massive piles of toxic fly ash, and tons of pollutants from natural gas plants? Because so far the answer is not good.
I believe you're talking about Earth, and the person you're responding to was talking about Mars. At least I don't think Mars had an oxygenation event or fossils?
She pointed out it was on a sign on the counter that I was looking at that moment, and had also been there when I dropped the car off the day before.
From TFA:
> To make things even more complex, many of these large companies are not traded publicly on the stock market, meaning their total number of holdings is not easily available to the public. Because Invitation Homes is publicly traded
1. Write "logging" data (observability, whatever) 2. Someone else starts using that to drive behavior 3. Change your logging, because it's just logging right? And stuff breaks.
To state it another way, anything you're emitting, _even internal logging_, is part of your API/contract, and therefore can't be changed carelessly. That problem is the same no matter what technology you use.
Usually the hard part is collecting the numbers and defending their validity.
But if we accept that it currently ignores any upper-bounds checks greater than v3, that's interesting. Does that imply that once Python 4 is available, uv will slow down due to needing to actually run those checks?