Over the past several articles, we've explored the stranger corners of PHP, JavaScript, Python, C#, Java, and, of course, Perl. Especially Perl. We've encountered variables that lie, loops that corrupt data, compilers that enthusiastically approve terrible decisions, and programming languages that seem to regard predictability as an optional feature. But there's a problem. We've barely scratched the surface of programming-language insanity.
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Jean-Luc Martel
Perl: An Exercise in Write-Only Programming
In Part 1, we explored Perl's remarkable ability to make ordinary programming concepts behave in extraordinary ways. We encountered expressions that change meaning depending on context, variables consisting entirely of punctuation, operators with their own memories, and data structures that create themselves when you look at them. We also learned that Larry Wall endorsed an unofficial expansion of Perl's name: Pathologically Eclectic Rubbish Lister. But we barely scratched the surface.
Let's Talk About the Pathologically Eclectic Rubbish Lister
We've explored PHP's questionable life choices, JavaScript's relationship with alternate realities, Python's talent for silently corrupting your data, C# quirks and the .Net identity crisis, and Java's industrial-scale production of factories. But now we've arrived at the main event. The granddaddy of weird programming languages. The Swiss Army chainsaw. Perl.
.NET: The Framework Formerly Known as Framework
In our last installment, we explored some of C#'s more surprising behaviors. But C# is only part of a much bigger story. A story involving multiple programming languages, competing user interface frameworks, a rather complicated relationship with open source, and enough product renaming to keep an entire marketing department employed for decades. Welcome to .NET. Or .NET Framework. Or .NET Core. Or just .NET again. We'll get to that. 1.
Java: Write Once, Run Anywhere, But Consult Legal First
In our previous installment, we explored Java's peculiar relationship with integer equality, collections that refuse to behave like collections, and the remarkable amount of engineering involved in concatenating two strings. But those were merely quirks of the language. The Java ecosystem is something else entirely. Because somewhere along the way, Java stopped being just a programming language and became an entire civilization.
Java: When Life Gives You Problems, Build a ProblemFactory
We've already explored PHP's questionable decisions, JavaScript's complicated relationship with logic, Python's ability to produce confidently incorrect results, and C#'s enterprise-grade surprises. Now it's Java's turn. Java is different. Java is serious. Java is strongly typed, object-oriented, carefully specified, and famously obsessed with backward compatibility. This is a language that makes you declare what things are before you're allowed to do anything with them.
C#: Your Code Compiled. That's Where the Good News Ends.
We've already explored PHP's questionable decisions, JavaScript's complicated relationship with reality, and Python's talent for producing beautifully formatted mistakes. Now it's C#'s turn. And C# is a different kind of beast. Unlike some of its more chaotic cousins, C# has always presented itself as a serious, carefully engineered programming language. Strong typing. Managed memory. A sophisticated compiler. A comprehensive runtime. The kind of language that wears a suit to work.
Python: while...else and Other Crimes Against Intuition
We've already explored some of PHP's more questionable life choices and JavaScript's remarkable ability to make perfectly valid code look like a practical joke. Now it's Python's turn. Python is particularly interesting because it has become the language of choice for data science, machine learning, and AI worlds. And understandably so. It's readable. It's expressive. Its ecosystem is extraordinary. You can go from a CSV file to a predictive model in 5 lines of code.
JavaScript: The Language That Gaslights Its Developers
After writing about PHP's greatest hits in the Weird Language Hall of Fame, it felt only fair to turn to JavaScript. Because if PHP is the language of historical baggage, JavaScript is the language of "this seems impossible, and yet it is fully specified behavior." JavaScript has a special talent for producing results that look like bugs, feel like bugs, and absolutely are not bugs.
PHP: 30 Years of Making Developers Say "Wait, What?" (Part 2: It Gets Worse)
Apparently, three examples of PHP weirdness weren't enough. In the original post, we explored how PHP considers "0" to be false, how array keys can silently overwrite one another, and how an innocent-looking foreach loop can unexpectedly modify your data. Those were fun. But PHP has been around for three decades, and you don't accumulate that much history without developing a few interesting personality traits.
PHP: 30 Years of Making Developers Say "Wait, What?"
With PHP suddenly back in the spotlight, I figured this was a good time to revisit one of the web's most successful, most criticized, and occasionally most bewildering programming languages. PHP has been powering websites for decades. It has evolved a lot, particularly through PHP 7 and 8, but it still carries some fascinating quirks. And I'm not talking about obscure syntax or features nobody uses. I'm talking about perfectly ordinary code that does something completely unexpected.
The Green Padlock That Almost Cost Me a Contract
Encryption is supposed to answer one question for the person sitting at the browser: am I really talking to who I think I'm talking to? On a corporate network running TLS inspection, the honest answer is often "not necessarily" — and most of the people relying on that network have no idea. There are serious risks if the setup isn't done properly, but raising that flag can lead to uncomfortable discussions.
A zero-disruption PodDisruptionBudget can block an AKS upgrade
Your AKS cluster upgrade is stuck. The control plane is waiting for a node to drain. The node is waiting for a pod to terminate. The pod is refusing to move. Look at the logs. The workload has a PodDisruptionBudget that allows exactly zero disruptions. It is doing exactly what it was told to do. Protect the application at all costs. Even if it means halting the cluster upgrade. To upgrade a node, AKS has to drain it. It cordons the node and evicts the pods.
NASA's Shuttle language survives only as a 1980 scan. I had AI rebuild it.
The complete specification of the language NASA wrote the Space Shuttle's flight software in is a 20-megabyte bag of page images. No text layer. Some pages sit at an angle. That document is IR-542, and nothing supersedes it. If you want to know whether a bit-string partition is legal on the left of an assignment, the answer is a photograph of a page printed in 1980.
Your AI Coding Agent Just Finished. Now Ask It to Attack Its Own Work.
AI coding agents are remarkably good at getting from “here’s what I want” to “here’s a working implementation.” They are also remarkably good at being satisfied with what they just built. That second trait is a problem. One of the highest-leverage habits I’ve picked up when working with coding agents is surprisingly simple: After the agent finishes a meaningful piece of work, ask it to perform an adversarial review of its own implementation.
How to Let gzip Find the Signal in a Pile of Documents
Suppose you have a directory full of text documents. Most are repetitive, padded with boilerplate, or otherwise low-signal. A few contain the useful material. You could read every file manually, feed them all into an embedding pipeline, or ask an LLM to rank them. Or you could ask gzip. The basic idea is simple: Repetitive text compresses well. Varied text usually does not. That makes compression ratio a crude but surprisingly useful proxy for redundancy. It will not tell you which document is best.
Climate Change and Rainfall Intensity-Duration-Frequency Curves: Overview of Science and Guidelines for Adaptation
Article Dans Une Revue (Article De Synthèse) Journal of Hydrologic Engineering Année : 2021 Climate Change and Rainfall Intensity–Duration–Frequency Curves: Overview of Science and Guidelines for Adaptation Mots clés IDF curves Rainfall extremes Climate change Climate models Convection-permitting models Clausius-Clapeyron relationship Guidelines Infrastructure design Origine Publication financée par une institution Licence hal-04976867 , version 1 (04-03-2025) Jean-Luc Martel, François P...
Limits of Blue and Green Infrastructures to Adapt Actual Urban Drainage Systems to the Impact of Climate Change
Introduction Over the last few decades, urbanization has led to increased impermeable surfaces and loss of permeable soil surfaces, disrupting the natural hydrological cycle by impeding water infiltration into the ground. This has resulted in an increase in both the volume and peak flow of runoff during rainfall events (Leopold 1968; Lee and Heaney 2003; Akter et al. 2018).
Climate Change and Rainfall Intensity–Duration–Frequency Curves: Overview of Science and Guidelines for Adaptation | Journal of Hydrologic Engineering | Vol 26, No 10
Introduction The design of most hydraulic engineering infrastructures is based on local intensity–duration–frequency (IDF) curves, which provide extreme rainfall intensity (mm/h) values for various durations (minutes to days) and return periods (years). Typically, IDF curves cover rainstorm durations from 5min to 24 h, with return periods from 2 to 100years.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Jean-Luc
Contact Jean-Luc, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack