If you haven’t read about it before, the term comes from the band Van Halen, who demanded that there were no brown M&M’s backstage. People thought it was just a crazy rock star thing, but David Lee Roth later explained that it had a purpose:

Van Halen was the first band to take huge productions into tertiary, third-level markets. We’d pull up with nine 18-wheeler trucks, full of gear, where the standard was three trucks, max. And there were many, many technical errors—whether it was the girders couldn’t support the weight, or the flooring would sink in, or the doors weren’t big enough to move the gear through.

… So just as a little test, in the technical aspect of the rider, it would say, “Article 148: There will be 15 amperage voltage sockets at 20-foot spaces, evenly, providing 19 amperes … ” This kind of thing. And article number 126, in the middle of nowhere, was, “There will be no brown M&M’s in the backstage area, upon pain of forfeiture of the show, with full compensation.”

So, when I would walk backstage, if I saw a brown M&M in that bowl … well, line-check the entire production. Guaranteed you’re going to arrive at a technical error. They didn’t read the contract. Guaranteed you’d run into a problem. Sometimes it would threaten to just destroy the whole show. Something like, literally, life-threatening.

My Brown M&M atm is AI-generated comments like this (first comment is referencing something like df = ... that they removed from the code, but left the comment, second comment is super useless):

# Assuming df is your DataFrame

# Show the plot
plt.show()

That probably means whoever I got the code from just copy/pasted whatever the LLM spit out, and didn’t actually think about the code at all.

What is a small detail that you pay attention to because it means there’s bigger issues to watch out for?

  • Phoonzang@lemmy.world
    41·
    19 days ago

    In a former job, I developed “software” (I clicked together some LabVIEW…) for custom designed scientific experiments, which many other researchers (mostly PhD students) would use. Wrote detailed SOPs for their usage, because everything was wonky and in constant evolution, and in some circumstances, data generated could be wrong. So I put a toggle switch with some cryptic acronym on the panel which was told to be flipped in the SOP when users reached the part where following instructions was really critical. The toggle switch did nothing but to log time and date and what user was logged in. When discussing weird data later on, first thing I did was to check whether that log existed, and if not heavily scrutinized the data with respect to errors that could be induced by not following the SOP.