This is a narrative from the guy who wrote the software that enabled "Collateralized Mortgage Obligations," one of the extremely complicated financial instruments that helped bring down Wall Street. It's an interesting perspective and a good read if you've got the time.

He feels bad, of course, but he can't bring himself to accept more than a little responsibility - nor, really, would I expect him to. He understood exactly what the program was doing; meanwhile, the firms kept pushing it to enable riskier investments, and the traders complained it didn't insulate them enough from the pesky details. Naturally, he made a lot of money off the software, but a lot more people made a lot more money off of it, and spent it on [insert wall street debauchery boilerplate]. He says he didn't expect his software to cause financial armageddon, but considering the people who were using it he's not surprised. He retired a few years ago and now raises oysters on Long Island.

It's a funny situation we programmers live in. Mercenary. People ask us for things they think they need. Maybe they do, maybe they don't. It's not really our position to editorialize. We quote them a large pile of money and, if they're rich and deluded enough, get to spend the next couple months to several years learning every minute detail of a business we don't care about so we can write software we're not interested in. When the day comes, your application goes one way and you go another way, on to the next client. And if you find out a couple years down the road that your application happened to cause a global economic meltdown, well, chalk it up to user error.

Today I discovered that an old business relation of mine had started a new local software company [dare I say... hyperlocal?] and was hiring Python programmers. I told my current boss/client, who said he was actually bidding against him on a project just this afternoon. I noted how incestuous the local IT sector is and joked that I would be on the project whether he got it or not. He called me a dick. I told him I was going to become a metaconsultant - get in on every software project in Buffalo, and let the web developers fight over who gets to bill it. I thought I was hysterical. He closed the chat on me.

- Z

I have a client who was very explicit that I should not be using standard book colors for Pantone matching, and is now wondering why everything looks all wrong. In addition to straightening out the mess, I've been able to put together a complete Pantone color table with Web, RGB, CMYK, Lab, and [why not] Grayscale approximations. This information is really difficult to find, and it shouldn't be. If it's useful to you, download it and save it for reference.

For everyone else: bunnies!


- Z

From the collection of the Museum of Bad Art

- Z

Can we quit with the shooting rampages already? Seriously.

- Z

Public service announcement: you should not be frying with extra-virgin olive oil. Spend some dollars and buy a bottle of peanut oil. Then spend some other dollars and buy a pound of bacon.* Then use this recipe to get rid of those boneless skinless tasteless chicken breasts that you've been freezer-burning.

Catfish Fried Chicken
1. Eat the bacon. Mmm, bacon.
2. But save the drippings in a little glass cup in your refrigerator.
3. Thaw the chicken breasts. If you wanted, you could pound them flat. If you wanted, you could also make schnitzel and join the Luftwaffe, you Kraut.
4. Breading: one cup of corn meal plus one tablespoon of chili powder. Next time I make it I'll probably also put in some fresh ground black pepper. Use as much of this as you need.
5. Heat two tablespoons each of peanut oil and bacon fat in a cast-iron skillet. If you don't have both, you've totally missed the whole point. If you don't have bacon fat you can substitute goose fat, lard, or butter. If you don't have peanut oil, skip the rest of the steps and stick your head in the oven.
6. Roll the chicken all around in the breading until it's evenly coated, and slide it into the frying pan.
7. This step is going to take a while.
8. Flip them over. They should look delicious on the bottom, which is now the top.
9. This step is going to take a little while too.
10. Flip them over again. They should look delicious on the top and bottom, which are now the top and bottom again.
11. Put them on a plate. Realize that you forgot to make side dishes.
12. Put the chicken in your mouth and chew. Notice that it is both crunchy and moist. Notice the super-subtle smoky flavor from the bacon fat.
13. Put $20 in an envelope and mail it to (e:zobar)

- Z

_______________

• The calculus of bacon.

1) Does thick-sliced bacon taste different than thin-sliced bacon? The answer is no. Buy thin-sliced bacon - there's more slices.
2) Low-fat bacon has more meat, but regular bacon costs the same and comes with a free half-pound of lard. Buy regular bacon and eat it twice.
3) Is a pound of bacon too much? Do you want to take your bacon Higher? Go to Spar's and they will give you exactly the amount of bacon you require, and it will rock your world.