Skip to main content

Programmers Arrested

It's rather unusual to hear of programmers, non-hackers, to be arrested for programming. But today's news announces the arrest of the programmers who build the applications that operated Madoff's financial empire of cards. Apparently the programmers are not being arrested for creating something illegal, but rather for "knowing" that their systems weren't complete (and therefore could not complete the financial trading operations)...

They were accused of knowing that the computer programs they developed in 2003 and 2004 contained fraudulent information used in U.S. and European regulatory reviews.

The SEC said O'Hara and Perez (the arrestees) knew that the "House 17" computer was missing functioning programs needed for actual securities trading.

In August or September 2006, they cashed out hundreds of thousands of dollars in their personal BLMIS accounts before meeting with Madoff and telling him they would no longer lie for him, the FBI and the SEC said.

The charges against the pair carry maximum prison sentences of 30 years and millions of dollars in fines. (Whole article here.)


As always, the news and the authorities position the situation in it's worst light. I certainly only know the details I read. But a couple of salaried programmers who had retirement accounts of a couple of hundred thousand dollars (a very normal figure after 15 years at a financial services company) and received a "huge" bonus of $60,000 (also a very normal yearly figure for top IT people working at financial houses) seem to be an odd target.

Is every IT employee involved in any financial system or business system development supposed to question the business process if what they're being told to develop doesn't seem complete or thorough enough? Would you, as a programmer or software architect, challenge a company Vice President making millions every year (versus your regular salary) when he says "this is what I need, go build it" if it seemed incomplete (and you pointed that out)? Would you quit over it?

Troubling.

Popular posts from this blog

Integration Spaghetti™

  I’ve been using the term Integration Spaghetti™ for the past 9 years or so to describe what happens as systems connectivity increases and increases to the point of … unmanageability, indeterminate impact, or just generally a big mess.  A standard line of mine is “moving from spaghetti code to spaghetti connections is not an improvement”. (A standard “point to point connection mess” slide, by enterprise architect Jerry Foster from 2001.) In the past few days I’ve been meeting with a series of IT managers at a large customer and have come up with a revised definition for Integration Spaghetti™ : Integration Spaghetti™ is when the connectivity to/from an application is so complex that everyone is afraid of touching it.  An application with such spaghetti becomes nearly impossible to replace.  Estimates of change impact to the application are frequently wrong by orders of magnitude.  Interruption in the integration functioning are always a major disaster – both in terms of th

Solving Integration Chaos - Past Approaches

A U.S. Fortune 50's systems interconnect map for 1 division, "core systems only". Integration patterns began changing 15 years ago. Several early attempts were made to solve the increasing problem of the widening need for integration… Enterprise Java Beans (J2EE / EJB's) attempted to make independent callable codelets. Coupling was too tight, the technology too platform specific. Remote Method Invocation (Java / RMI) attempted to make anything independently callable, but again was too platform specific and a very tightly coupled protocol. Similarly on the Microsoft side, DCOM & COM+ attempted to make anything independently and remotely callable. However, as with RMI the approach was extremely platform and vendor specific, and very tightly coupled. MQ created a reliable independent messaging paradigm, but the cost and complexity of operation made it prohibitive for most projects and all but the largest of Enterprise IT shops which could devote a focused technology

From Spaghetti Code to Spaghetti Connections

Twenty five years ago my boss handed me the primary billing program and described a series of new features needed. The program was about 4 years old and had been worked on by 5 different programmers. It had an original design model, but between all the modifications, bug fixes, patches and quick new features thrown in, the original design pattern was impossible to discern. Any pattern was impossible to discern. It had become, to quote what’s titled the most common architecture pattern of today, ‘a big ball of mud’. After studying the program for several days, I informed my boss the program was untouchable. The effort to make anything more than a minor adjustment carried such a risk, as the impact could only be guessed at, that it was easier and less risky to rewrite it from scratch. If they had considered the future impact, they never would have let a key program degenerate that way. They would have invested the extra effort to maintain it’s design, document it property, and consider