Commentary

Serdar Yegulalp
 

Hail And Farewell, Part One

The only constant thing is change, and change has come my way. As of the end of 2009, I'll be leaving InformationWeek -- so over the next couple of days I thought I'd sum up a few points gleaned during my time here.

The only constant thing is change, and change has come my way. As of the end of 2009, I'll be leaving InformationWeek -- so over the next couple of days I thought I'd sum up a few points gleaned during my time here.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

1. Linux is not the be-all and end-all of open source.

This might seem crashingly obvious to many people, but it bears repeating. Linux is bandied around almost unilaterally as the most obvious example of open source development at its finest. True, it's quite a success story, but it's only one of many -- and not the only model to follow. Not in its licensing, not in its implementation, and not in the stances adopted by many of its most vocal proponents. It's only one possible approach of many, and it's too easy to forget open source can -- and must be -- a panopoly.

2. Proprietary software isn't going anywhere. Neither is open source.

And it doesn't mean open source and proprietary can't teach each other a few new tricks. Most of the successful businesses that use open source as part of their strategy have taken a hybrid approach -- either open core or open extras, depending on the market they're addressing and whatever existing development/business model they already have. (It's a lot harder to switch to open source than it is to start there from scratch, no matter what you tell yourself.)

3. Open source requires people, not just programs.

The brouhaha over MySQL brought this one back to the surface recently. Software is made by people, developed by people, and kept alive by people. Open source makes it easier to keep a project alive, but doesn't magically create a solid development team around a project. That requires effort, charisma, money, or some combination of all three of those things. To coin a phrase: People before packages.

4. Engineering should come before ideology.

Open source should be thought of first and foremost as a software development strategy, not as a magic bullet for creating digital democracy everywhere. It can be one of many ways to tilt the axis of the world that much more towards freedom and justice, sure -- but it's also too easy to see everything as a nail to be pounded with that particular hammer. Most people pick the ideology that squares with their present and past behavior, rather than shaping their behavior to fit a professed ideology. Expecting them to swap the cart and the horse in favor of benefits they may never reap in their particular case is absurd.

There's a few other points, but I've found most of them fit into one corner or another of the four I've quoted here. Come Monday, I'll look forward and muse about what awaits us there.

Our "A New IT Manifesto" report looks at a variety of new approaches and technologies that let IT rebels take on a whole new role, enhancing their companies' competitiveness and engaging their entire organizations more intimately with customers. Download the report here (registration required).

Twitter: Me | InformationWeek
Facebook: InformationWeek


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links