Zcom_simple

Hello,

Blogs are a familiar feature on the internet - where users post content in an accumulating manner, with comments, and search options, etc. They facilitate expression and exploration, and via attached comments, also debate and synthesis.


Reading and
Navigating Blogs

Our blogs are quite powerful. Each writer can post, as is typically the case. Sustainers who have the option can also post, however. All Blogs appear in the blog system, and sometimes also in content boxes the top page of ZNet - and always via the left menu of the top page - and can be found via searches, etc.

Commenting on blogs follows the blogs, attached at the bottom, and blog comments, like all others, are also visible in many places that show comments including in the forum system. In addition, the entire blog system gathers content for everyone - but one can look at the accumulating content in many ways.

  • For example one can look at one writer's efforts - so one is seeing what is effectively a blog system for that one writer, or Sustainer.
  • One can also look at the content by topic, seeing blogs that are tagged as being about a certain topic - or place, as well. Thus, when doing that, it is a blog system about a topic, or a place, with many contributors.
  • One can look at only writer blogs, or only sustainer blogs, as well.
  • One can look at blogs for particular Groups, too.

All this is easily done using the left menu. Searches allow even more variables and refinements.


Creating Blog Posts

If you are a Sustainer with permission, and are logged in, you will see a link in the left menu for you to post a blog - and you can use that to post one, and then tag it various ways (such as with a topic or place, or a group tag), and once you do, it is in the system with you as the author.

You can also use the console button to the left to post a blog - anytime and from anywhere in the site, as long as you are logged in.

Meanwhile, enjoy the blogs - and, by the way, if you are a Free Member or a Sustainer with a ZSpace page, of course you can put one or more content boxes on it, pulling blog links of any sort you may want to filter for, for example, by you or by your friends or by others - and by topic, about places, for groups, etc.

Blogs

Boyd Collins's Blog

Web Address: http://www.zcommunications.org/zspace/boyd
Bio: Peace activist and blogger for the past 5 years.  I currently run the Nonviolent Jesus blog, http://nonviolentjesus.blogspot.com.  (More)

All Collins Blogs

Irrational Designs: A Parecon Critique of the Software Industry

By Boyd Collins at Feb 08, 2009


Change Text Size a- | A+

The best operating system in the world did not require billions in venture capital.  It was designed by students and hobbyists during their disposable time.  In other words, it was designed and produced using participatory production methods and has now achieved “market” penetration that seriously threatens the “efficient” capitalist monster Microsoft.  The name of this operating system is Linux and I believe it offers a paradigm for a participatory method of production that could vastly improve the quality of software in the future.  The software industry has succeeded in spite of and not because of capitalist methods of production.   Software flourishes in freedom, in networks of equality, driven by bursts of uncontainable creativity which have been perverted and exploited by capitalist methods of social production.

Good software requires time, long periods of intense and lively concentration, mathematical and logical talent, and a few basic tools.  There is no more wasteful time sink in software engineering than having to work around the consequences of the proliferation of poorly designed and rushed software.  This proliferation is the result of sophisticated marketing campaigns which have resulted in huge profits for select corporations while doing more damage to the potential of software than any other factor.  The logic of software contradicts the logic of capitalism at each step of its development.

Many will argue rather persuasively that competition is the lifeblood of software.  As a software professional, I heartily endorse this proposition.  But we must distinguish between two meanings of the word “competition”, which are typically slurred together by the corporate media.  The competition that every software professional celebrates is competition between designs and implementations in which the one with the best features, most performance, and highest level of extensibility and interoperability flourishes over its rivals.  But this is not the competition which the mavens of our mega-corporations inflict.  And the destructive competition in which they thrive is at the root of a crisis that can only be solved by a full embrace of participatory methods of software production.   

The competition which has rotted our technological infrastructure is centered on marketing, not quality.  Those corporations who own the marketing machines can and do drive absolute garbage onto consumer’s PCs.  You will often hear them explain that they cannot afford to care too much about quality, because this would interfere with optimal market timing.  A prime example is the recent release of Vista, which is now widely recognized as an immature operating system that was rushed to market.  Dozens of major examples could be cited along the same lines.  The dirty secret of software is that it is a hard and complex science that that requires the attentive capacity of a jewel cutter to do properly.  It can be done, but devotion to craftsmanship is what truly allows it to succeed.

The conditions of the modern software marketplace militate against such care and attention on every side.  Unrealistic release schedules are devised by project managers who make guesses based on nothing more optimal time to market.  Of course, they “consult” with developers who are encouraged to be “honest” in their time and effort estimates.   But those developers realize all too well that true honesty would get them dismissed and replaced by others whose honesty was more closely tuned to the demands of market timing.   While most developers want to create a product that is focused on user value, the market constantly perverts these “use-values”, resulting in buggy and insecure products that waste enormous amounts of time.  Good software exists, but its survival is not a market value, but a happy and often unrepeatable exception.

The profit motive has been the incubus that has sucked the life, creativity, and potential out of the software industry, whose chaos and inefficiency mirrors the chaos of the capitalist production from which it arose.  What software engineers value is the use-value of the software they create.  What capitalism values is the surplus value (the difference between the cost of developing software and the licensing fees it commands in the market), not the ability of the software to interoperate successfully with software designed by rival firms.  Yet this latter characteristic is precisely what leads to the greatest multiplier of use-value.   The generally poor effectiveness of software is the result of the fact that it is produced by competing islands of specialized vendors who have little reason to interoperate with others and strong motivations to subvert the operation of their rivals’ work.  Standards organizations attempt to bridge this gap, but support for the standards produced by these bodies is notoriously low even by the major players who have the most to gain from it.

The nature of good software is to reach out and create networks of interoperability, but such interoperability can flourish only in free productive relationships unconstrained by competing profit interests.  On a truly level playing field where only the quality and usefulness of the products mattered, we would finally be able to uncover the true potential of software to improve human life.  But such a utopian expectation can never be fulfilled until the system of production gains overall direction and unified planning.  The idea that quality will arise from competing islands of entrenched marketing interests is as absurd as believing that unregulated financial markets will self-correct.

 

589727

By Martin, James at Feb 09, 2009 15:33 PM

I absolutely agree with your final point:

"The idea that quality will arise from competing islands of entrenched marketing interests is as absurd as believing that unregulated financial markets will self-correct."

In my schizophrenic existence as a test engineer for a closed-source software corporation (in the financial markets sector no-less) by day, versus my nights spent participating actively in various free software projects; this post really strikes a chord with me.

For the past few years I've been considering how to make a move away from my "day job" and into an organisation that values and strives for quality software that benefits its users, while encouraging craftmanship among its workforce. I firmly believe that such an organisation does not exist if it's competing in the capitalist mainstream.

Unfortunately, some of the experiences I've had within the free-software community has not been exactly text-book paresoc (if such a thing exists). Many projects harbour quite small, close-knit cliques of elitists that do not encourage participation and appear to actively discourage new ideas or challenges of their structure.

Reply this comment

Comment_reply

Person

Re:

By Collins, Boyd at Feb 09, 2009 22:16 PM

I agree with you about many open source projects and I have been a participant in them as well. However, I would argue that the elitism one often finds in them is more a product of the capitalist indoctrination that most software professionals undergo than anything directly pertinent to effective software design. Good software in and of itself flourishes in an atmosphere of craftsmanship and benefits from as much knowledge sharing as possible, like any science. Elitism and secrecy often hide bad practices that tend to make an appearance at inopportune moments. Of course, developers usually adhere to the scientific rationality that tends toward the command and control structure of the economic hierarchy. Technology usually functions as a form of social control and domination and those who feed this beast often take on the characteristics of the beast. My argument is that this is not an inherent feature of software technology as such, but a consequence of relations of production that reinforce such hierarchies.

Reply this comment

Loading_border