Remembering Progeny

Two weeks ago, I heard that Progeny Linux Systems of Indianapolis had closed its doors for the last time. The end was a long time coming – in fact, six years longer than I predicted. All the same, I paused last week for a bit of nostalgia. Working for the company in 2000-01 gave me my first sense of my potential and gave me a sense of self-worth at a time when I badly needed it.

I first heard of Progeny through Bruce Perens. I was talking to him over the phone for a story I was doing for Maximum Linux. When our business was done and we were chatting, I happened to mention that I was looking for work. At the time, Perens (whom I'm calling by his last name so that this entry doesn't sound like a Monty Python skit littered with Bruces) was running a venture capital group that had just funded a startup run by Ian Murdock, the founder of the Debian GNU/Linux distribution and his partner John Hartman. Would I be interested in doing marketing and communications for the new company?

Somehow, I managed not to gibber incoherently with excitement, and told him I would. But I admit I danced around our townhouse when I got off the phone.

A phone interview and a week or so later, and I was on a plane to Indianapolis, unsure whether the job would work out. I was a bit worried about the cost, since I had quit Stormix Technologies a month previously, but determined to enjoy the adventure.

I was met at the airport by Ian and John and a couple of coders – John Goerzen and possibly Branden Robinson. They whisked me away to a Greek restaurant, where I quickly realized that these guys had serious chops. I had thought for a while that Stormix was the big time, but I realized that, in going to work for Progeny, I was jumping leagues.

Somehow, I convinced them that I would be an asset. I may not be able to write code for a “Hello, World

______________________

--
Bruce Byfield (nanday)

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

nice article

Anonymous's picture

I have the same feelings for my first company - it was 1998-2001, of course during the dot com era and I thought the company was gonna go big time. It didn't but I had more exciting projects than my friends who took more conservative jobs.

Webcast
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers

Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.

Learn More

Sponsored by AMD

White Paper
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions