ijk
Joined 14 years ago
Joined 14 years ago
Now math gets to deal with that same reckoning. They were already well on their way there with previous Lean proofs, but this has pushed things beyond that horizon and I'm not sure some of the mathematicians are ready for it.
There's a number of places that destroyed vast amounts of data in the wind down of ZIRP that probably regret it now.
The yellow journalism era, on the other hand, was a little closer to the rich owning the press.
There's a lot of work in the humanities about different aspects of good writing, but that's not quite the same thing. And anyway they tend to assume a pre-existing level of writing ability. Students are supposed to learn good writing through practice; there are rules and exercises but they're incomplete.
It's relatively easy to avoid being that egregious about it if you're a little bit patient on construction permits and power contracts.
NIMBY opposition to datacenter construction is orthogonal to that, except insofar as in both cases the construction will gravitate toward places that won't or can't object to the construction.
But I have found that sometimes the best use of an LLM is to write code for symbolic AI.
With modern tool calling I wonder if a better way to go about it is for the LLM to express the program changes as a function or otherwise use an editor that auto-balances parens. There's a lot of relatively simple tooling that makes it easier to write in a Lisp. The languages tend to lend themselves to being straightforward to check like that.
What's special about Lisp's repl is that it's perfectly possible to construct your entire program in the repl, testing each addition live as you write it. (Many Lisp-focused editors assume you'll want to do this, such as Emacs making it easy to run the interpreter on a single function in a file.) That tooling is lost if you just try to one-shot the file, and before 2026 the majority of LLMs originally just tried to one-shot every file.
But, just like a lot of early LLMs had huge problems with whitespace and numbers because the tokenization was taking efficiency shortcuts that made sense for text but absolutely wrecked code syntaxe, I wonder if the current optimizations are badly formatted for Lisp.
At the very least, using a varient like Clojure that also uses [] and {} in addition to () might help.
Or maybe I've just been sleeping on the power of Javascript AST.
It's hard to find non-paywalled sources for business analysis, but from what I can find it'd be about 20%.
There's a lot of moving parts that go into it, and even experienced teams have difficulty finding the fun. It's extremely common that games that are now popular and beloved weren't very fun until a few months before they released.