News for hackers. Stuff that matters.

lickonographic

Re:" and the proof is checked in Lean" on Monday November 16, 2026 @11:35AM (#50519528)
Oh I know how deeply we think about these things in the academy. I also know how practice, not least of all in industry, falls short of the depth of the theoretical thought.

I hear and participate daily in discussions about automation, computation, programming - languages, environments. I have no illusions about the pinnacle of theory filtering down to how people spend their time, how organizations their resources, or how people talk about these problems every day in the context of real world project which tie up very limited resources pursuing things the theory should have made very clear to be out of reach for several decades now.

"What about errors made without AI" is not a proper argument.

We don't need a fault-free method of producing software to realize that any levers used in the process can only amplify errors and their consequences. Sometimes the answer is to go slower and make it correct before pouring wattage on the system. Sometimes the answer is go go fast and break things.

The only certainty should be that there is no universally correct answer to how to seek answers. Sometimes an ad hoc app built quickly without looking at code is the best solution. It certainly shouldn't be a surprise that any gains therein are not without cost. Or that any such machinery can only ever make knowledgeable people doing slow work on fundamentals more necessary, not less.

Re:" and the proof is checked in Lean" on Monday November 16, 2026 @07:24AM (#50516851)
I think the deeper problem - an I am reading Computational Reflections by Cantwell Smith and that might be colouring my view - is that fundamentally it comes down to the interpretation of what the code or the math says.

The very meaning of interpretation in computer science is at odds with the use in philosophy of language and that is symptomatic.

We're still fundamentally trying to advance Hilbert's program. It's like Göedel's work hasn't sunk in to our collective reasoning about reasoning. It just doesn't seem possible to build a self contained correct and truthful system of symbolic logic. Truth is in the relationship of the system with other systems.

Automating mathematics, like automating software engineering, or automating automation, are all self contradictory propositions. Anything of what we build only ever means anything in how it interacts with us. I mean, people will go round and round in this forum discussing semantics and the meta implication of these unceasing discussions never seems to hit home. Namely, that there is no universal, truthful, correct, system of symbolic logic. It seems in fact impossible to have one. But the results that indicate this impossibility are built with a system of symbolic logic and the validity therein is contingent on people's understanding and, like all symbolic logic systems (including the ones that states the limits to universal symbolic logic systems) they are bootstrapped from axioms one must chose at the start or by default and they can never be fully proved by the very system built atop them.

Interestingly, at least for me, the author of the original "worse is better" series of essays (they're still online) has flip flopped many times on his instance.

I think it speaks to the core of the "software crisis" literature which is its own genre. Big Ball of Mud, No Silver Bullet, The Three Cultures of Computer Science and so on.

Correctness and expediency are at odds and we have to make choices along these trade-offs constantly. The costs each imply accumulate. I don't think there can ever be a simple answer to the question of how to design and run complex systems. Every facile argument about this or that tool chain devolves into flame wars precisely because these arguments are about "the right way" (or the wrong way) to design and run complex systems and there simply isn't any (right or wrong).

"Systemantics" is a perpetual gem that should be High School required reading.

Re:A short explainer on how El Niño works [video] on Monday November 16, 2026 @06:51AM (#50516574)
Spot on. The discourse that fossil fuels are necessary for wealth is propagated by those whose wealth is built on fossil fuels. It is entirely possible to have an even more prosperous society if all the energy sources isn't tied to the profits of the "dig up and pump fuel" concerns.
Again, the choices are not "let employer or Amazon record everything"

And you're equating passing the video and audio stream to some inference API for automatic transcription with merely storing video on premise or in cloud which is a gross misrepresentation of my objections.

Again, because you are intentionally misinterpreting my point: there is a lot of space in between hearsay and passing a stream for third party auto transcript APIs and somewhere in there is proper, reliable, and controllable documentation.

Also, like everything else ever to be framed as a technical only problem, it has social and political dimensions. From you to the corporate overlords "employer" and "cloud provider" there are a lot of layers and ignoring that is part of the defeatist attitude I denounce.

Privacy and documenting adversarial interactions are entirely orthogonal

There is zero need to stream video and audio to third party APIs to document a meeting.

In fact, an automatically inferred transcript is arguably riskier than no documentation at all.

Recording meetings has been a thing for literal decades and it can be done in very privacy safe ways. A binary view of privacy is defeatist. Data governance is not an all-or-nothing proposition.