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.

Comments URL: https://news.ycombinator.com/item?id=49003337

Points: 1

# Comments: 0

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%.

Of course the first thing we replaced with AI was artists, so expect more exclusively as the lower rungs of patronage clients fall off the economic ladder.

There was kind of a fatal mis-match between the questions being asked and the intended kind of questions that were being answered. The actual asks were often incomplete diagnostics of the questioner's current problem, frequently focusing on the wrong thing (because if you don't have the full knowledge of the thing you're going to be prone to incorrect assumptions of the diagnosis). SO's intent, though, was a more mathematical "here's the question, here's the programming concept that explains it" so you get the best explanation of how a linked list works under a completely unrelated problem. Which is fine, but the site's culture and design only partially acknowledged the disconnect.

The whole site developed a reputation of being something approximating the reverse of the comments under recipes that substitute lard for cream and wonder why their cake tastes funny. Lots of questions of "How do I implement this functionality in Y? We can't change our tech stack because of other factors, so it has to be Y" questions answered by "If you just use Z instead you wouldn't have these problems" and "closed as a duplicate of this question for how to implement the non-Y version" when there was a perfectly fine way to do it in Y.

There are many examples of this in nature. (And in Nature [1].) One interesting one that I think is unknown to many people is limnic eruption. A lake can absorb quite a lot of CO₂, for example from volcanic gases. Dissolved CO₂ is invisible, so the lake can look quite ordinary, but the build-up turns the lake into something approximating an unopened carbonated soft drink. If the lake is deep enough and the layers don't mix frequently enough to relieve the pressure, it can build up to the tipping point where the lake will suddenly explode, flooding the nearby landscape and releasing an invisible CO₂ cloud, which will proceed to kill the surrounding life by asphyxiation.

The conditions required for a limnic eruption are rare, though there were two incidents in Cameroon in the 20th century.

It's entirely possible that the build-up of hostility on Stack Overflow were survivable as long as it didn't build up to a level that exceeded the community's ability to absorb it. But an exogenous shock or the community shrinking could upset the balance, with hysteresis making the change difficult to reverse.

[1] https://www.nature.com/articles/s44458-026-00063-5

[1] https://en.wikipedia.org/wiki/Graduate_student_employee_unio...

Which is not to say that conditions in graduate schools (or academia as a whole) are great. But the unionization process is entangled in the legal framework around unions in the United States.