Recent Best of…

Our "best" articles of years past.

Jul 2024

Classic WTF: Cluster#$%&

by in Best of… on
Reliability is its own, very important art. Unless you're, say, Google, you shouldn't write your own reliability systems, but instead buy solutions from a vendor. Just not this vendor. Original. --Remy

Image credit: 'Mark Bowytz' - REMEMBER THE KRAKEN!!!It was a little past 4AM when Massimo's support pager went off, jarring him awake. Without even looking at the pager or logging into his laptop, he flipped on the television to Channel 242: the Video on Demand channel for the Italian TV broadcaster that he worked for.

Nothing.


Classic WTF: Python Charmer

by in Best of… on
When comparing your language to a snake*, be careful to not get bitten. (*Yes, I know, the name of the language is a reference to Monty Python, not snakes). Original. --Remy

"I don't have a whole lot of experience in Python," writes Jakob, "in fact, when I was hired, the only thing I knew about the language was that whitespace was important."

"Fortunately — actually, unfortunately — it doesn't take a whole lot of experience in Python to recognize that my company's codebase is... well... sub-optimal. Submitted for your approval is a method used to generate a password, found in our network security library."


Classic WTF: What's in a Name?

by in Best of… on
We continue our summer break. Sometimes, you need to make a bad choice in your design, and you can often "fix" that, with documentation. "Don't touch the sharp pointy bit." But, not to spoil the ending, sometimes the documentation raises more questions than it answers. Original. --Remy

The year was 1993, and that meant one thing: Old Iron was finally ready for the scrap yard retirement after nearly fifteen years of faithful service to the university. Technically, the MVS-based mainframe had been well past its prime for quite a many years, but since it was used primarily as a data repository for research projects, no one seemed to mind. But what they would mind, however, was any sort of downtime in the transition to the new, UNIX -based research computer, so it was up to Todd M. Lewis to figure out how to ensure things went smoothly.

In order to give researches the opportunity to learn their way around Unix and adjust their processes for the new environment without disrupting ongoing work on Old Iron, Todd set up a migration process that would pull MVS data sets from the backup system (as not to interfere with “live” data sets users may be using) and copy them to an archive on the UNIX server. From there, users could check out copies from this archive and work with them under UNIX to hone their processes. If they screwed up the data, they could just check it out again from the archive.


Classic WTF: XML Anybody?

by in Best of… on
We're taking our summer break, which means we reach back into the archives and find some classics. This one teaches you everything you need to know about generating XML. --Remy

XML is an absolutely wonderful innovation. It allows us to easily describe and share just about any data immaginable. Of course, there's always gotta be someone (as Tim points out) who has to go and ... well ... see for yourself ...


Classic WTF: For Each Parallel

by in Best of… on
It's a holiday in the US today, where we celebrate with a lot of explosive-induced accidents and emergencies. Instead of holding a cherry bomb until it's too late, let's instead look at some explosively parallel code. Original. --Remy

Parallel programming is hard. For all the advancements and tweaks we've made to our abstractions, for all the extra cores we've shoved into every CPU, deep down, software still carries the bias of the old uni-tasking model.

Aleksei P works on a software package that is heavily parallel. As such, when interviewing, he talks to candidates about their experience with .NET's Task objects and the async/await keywords.