Tuesday, April 24, 2012

Hackstability: how big systems can survive their own success

Just read a fascinating article by Venkat here on ribbonfarm, positing a third path for systems to evolve between total replacement and reengineering and entropy collapse. Most interesting is his example of city technology, where a major old city teeters forever on the brink of collapse, but because the people who /live/ there keep hacking the systems that are the city, the systems keep working.

I've experienced this on the small scale. While at [fill in major technology company here], we had genuine legacy software, a server that was notoriously both fragile and single threaded, so that if any of the dozens of computers that talked to the server threw it a curve, lost their mind, or whatever, the entire server hung, and the factory stopped moving product.

At the time, my thought was "Well shit, guys, write a new one that isn't single threaded. While you're at it, make the damn thing so it can span cluster nodes and load share automatically too." In terms of the article referenced, however, paying interest on the technical debt - that is, the deficiencies of the server from crappy design, kludges, and so forth by having the team of support people I was on monitor the thing and restart it as necessary were cheaper than the paying the real costs to design and implement a replacement without those deficiencies.

The article goes further though. It talks about how technology like the much hated server discussed above becomes non-disposable, how it accretes so much interdependency with other things that it /can't/ be ripped out and replaced. And that's where the concept of hack stability comes in. The humans who maintain the server can continue to hack it, so long as their (often undocumented, non-organized) knowledge is preserved across generations of support people (high turnover) and keep the system either going indefinitely, or at least guide it into a soft landing instead of an uncontrolled crash.

All interesting in terms of computer systems, but the author is extending the reach of this concept to /everything technology has colonized/. That is, the whole planet.

Read the article. It's good. Expect to see it in my work at some point. :)


Monday, April 9, 2012

Commodore 64 Creator Jack Tramiel Dies

The first computer I ever touched was a Tandy TRS80 model 3, which my mother borrowed from the school district she taught for one summer. The first computer I owned was a Commodore 64. I can't tell you how many hours I sat behind that thing learning to program, writing papers, goofing off. I can tell you that I used it from my junior year in high school, 1984 or so, through high school, through undergraduate school, and that I surrendered it only in 1990 as I began grad school and really needed a PC. Until the computer I'm writing this on, it was my longest lived computer ever. Hard drive? Who needed it? I had a 1581 800k floppy drive (and a burst mode rom chip to drive it.) It was fast, three or four floppies would hold all the software I owned, and it didn't make the hideous sounds the 1541 drive did. Graphics? Got 'em. Sound? Best in the industry until Mac, Amiga, and so forth came out. Truly a wondrous thing. And now the man who built both it and the company is gone at the age of 83. From a once-upon-a-time budding young nerd who still remembers how much fun computers were back then. A toast to you, sir. And farewell. -JRS

Thursday, April 5, 2012

New Music to Write To

New Music to Write To: Trent Reznor and Atticus Ross – The Girl With the Dragon Tattoo (Soundtrack from the Motion Picture). On iTunes here. -JRS

Blog Archive