The second that road gets defunded by the public coffers, guy with tractor would show back up.
The second that road gets defunded by the public coffers, guy with tractor would show back up.
They'd quickly find out when they're not being subsidized by the general public and people actually have to pay their way to use their vehicles through tolls to people amortizing their road maintenance costs, that the smaller more pedestrian safe cars are the ones that make sense to operate.
> pay whatever the market rate
would only work if there is a market. And infrastructures like roads are a natural monopoly[0], so there could be no market.
It's one thing to fudge the language in a report summary, it can be subjective, however numbers are not subjective. It's widely known LLMs are terrible at even basic maths.
Even Google's own AI summary admits it which I was surprised at, marketing won't be happy.
Yes, it is true that LLMs are often bad at math because they don't "understand" it as a logical system but rather process it as text, relying on pattern recognition from their training data.
Rightly so! But LLMs can still make you faster. Just don't expect too much from it.
See for example the depletion of the Ogallala aquifer, which is at the same time an existential threat to to farming and caused by farming.
This, so much this!
(It is not intended to be an insult of any sort. It is a serious question. I do not know anyone who does this and I cannot imagine myself being productive at all. I want to compare WPMs on a keyboard vs. on a phone as well.)
I never tried programming on it but I can imagine a world where the only computer i own fits in my pocket.
Question: how to encourage such patterns within a team? I often find it difficult to do it during code reviews and leading to unproductive arguments about "code style" and "preferences".
Funnily, these arguments do not happen when a linter pops a warning instead...