A conversation with a coworker re-triggered an intrusive thought that I find myself returning to regularly while working in a firm in the grips of AI influences:
Teams and engineering processes are like fish in tanks. There's a careful balance of the nitrogen cycle that keeps delicate organics alive; above a certain pH, it's just not plausible to believe things will keep working. But to understand effects, we have to take into account causes and add the effect of time.
I hereby coin the term "Ptolemaic Code" to refer to software that appears functional but is based on a fundamentally incorrect model of the problem domain. As more code is generated by AI, the prevalence of such code is likely to increase.
1/7
Scan of the paper Design Considerations for a Functional Programming Language by Rod Burstall, from the Proceedings of the Infotech State of the Art...
Re: last boost https://chaos.social/@dpk/115589097803252590
That OCaml PR is textbook open source in the era of vibe coding...
It's got everything:
- PR submitted without the author acknowledging they didn't write it and don't understand it.
- Copyright laundering.
- "I just wanted to get it done!" versus maintainers who know they have to live with code contributions for years.
- Zero-effort pasting LLM output as reply to real people's thoughtful questions. (At least the author acknowledged what they were doing that time.)
- It doesn't matter that it's hard to review because "AI has a very deep understanding of how this code works."
- "Beats me. AI decided to do so and I didn't question it."
If this is our new world then it's going to turbocharge maintainer burnout.
(If you don't want to read a quite long often depressing thread, would still recommend reading this well reasoned comment by one of the maintainers:
https://github.com/ocaml/ocaml/pull/14369#issuecomment-3556593972 )
Fucking. Hell. https://github.com/ocaml/ocaml/pull/14369