Softpanorama (slightly skeptical) Open Source Software Educational Society

May the source be with you, but remember the KISS principle ;-) Softpanorama Search

Workagolism and Chronic Work Overload Bulletin, 2002

Slashdot/Is Programming a Dead End Job

Not always true (Score:4, Insightful) by kaladorn on Thursday April 25, @03:41PM (#3411001) (User #514293 Info | http://slashdot.org/)

My boss (our VP and I think CTO) is the developer of utmost Deep Magic. But of course, we're a relatively small company. But to take the other side of the coin up, I know of developers who made more than their managers (as one of my classmates ascended to management, I know several of the lead developers were making significantly more than he was). There are two or three GOOD reasons why managers make the big bucks. In theory, they are the RESPONSIBLE ones. The buck stops there. Programmers can often excuse problems as being the result of other people's work, their deadlines, etc. But a manager has no such refuge. That responsibility should be commensurately rewarded.[1] Also note that some highly paid programmers who make more than their management treat their management like inferiors. I've seen this. At the end of the day, some of the geek community only respect salary or other raw displays of power and authority. Sad but true. Lastly, good managers are worth their weight in gold and do significantly benefit a project. They coordinate people, resources, and customers. They manage customer expectations, attend to the wellbeing of their managed, and ensure that all required resources are forseen and in place when required.[1]. So even though the comment about programmers not getting paid more than managers has exceptions, there are some good reasons for things to be as they are. [1] - I know very damn well that the theory often doesn't match practice. For some reason, many companies keep inept management in place, I suspect because the next management level up is equally inept. I've had precisely three fair to okay managers, 1 really great manager, and several of the nightmarishly inept variety. But why companies keep incompetent managers in positions of power despite all the damage this causes is an utterly separate issue from the reasons why managers are paid more than programmers. Valid, but different.

Cliff said it all (Score:3, Insightful) by Havokmon (rickNO@SPAMhavokmon.com) on Thursday April 25, @02:36PM (#3410478) (User #89874 Info | http://www.havokmon.com/ | Last Journal: Thursday September 27, @05:18PM)

People who are in this career for the money or the prestige may not like it after a while, but the people who are in this for something else will tolerate quite a bit before deciding to opt out. And is exactly why Loki lasted as long as it did..

[ Reply to This | Parent ]

Re:Cliff said it all by hendridm (Score:1) Thursday April 25, @02:40PM

No way (Score:4, Insightful) by dciman (kybwilli@indiana.edu) on Thursday April 25, @02:37PM (#3410485) (User #106457 Info | http://php.indiana.edu/~kybwilli/)

I think that programming is by NO means a dead end. Sure there is a bit of a tough time right now with the economy in its current state. But, we are just now seeing an emergence of whole new computational fields. These mainly being in the life sciences arena. Genomic sequencng projects are quickly overloading scientists with raw data that someone needs to turn into usefull information. The area of developing these tools is vast. Possibly more important will be people who come up with better algorythms for predicting protein structre and interactions based on sequences. This is an amazing field that has the promise of keeping computre scientists, biologists, and bioinformatics people busy for decades to come. I think the field is ready to make leaps and bounds.... and most definitly not a dead end.

Embedded.com - Is This A Dead-end Career

Become a dentist, CPA, or lawyer and odds are you'll be practicing that profession on a more or less daily basis till the day you retire. That seems less likely for engineers and firmware developers. How many EEs or software folks do you know in their 60s who still work as techies? How many in their 40s?

Though I haven't the statistics to support it, my observations suggest that embedded systems development is a field dominated by young folks -- say, those under 35 or so. Middle age seems to wean folks from their technical inclinations; droves of developers move towards management or even the dark side, marketing and sales.

Is salary compression the culprit? My students, all of 21 and armed with a newly minted BSEE, get entry-level jobs at $50-60k. That's an astonishing sum for someone with no experience. But the entire course of this career will see in general less than a doubling of this number. Pure techies doing no management may top out at only 50 percent above the entry-level figure.

Consider that $70k or $80k is a staggering amount compared to the nation's average mid-$30k average family income -- but even so, it's quickly swallowed by the exigencies of middle-class life. That $50k goes a long way when one is single and living in a little apartment. Life happens fast, though. Orthodontics, college, a house, diapers, and much more consume funds faster than raises compensate. That's not to suggest it's not enough to live on, but surely the new pressures that come with a family make us question the financial wisdom of pursuing this wealth-limited career. Many developers start to wonder if an MBA or JD would forge a better path.

What about respect? My friends think "engineer" means I drive a train. Or that being in the computer business makes me the community's PC tech support center. "Doctor" or "VP Marketing" is something the average Joe understands and respects.

Is tedium a factor? Pushing ones and zeroes around doesn't sound like a lot of work, but getting each and every one of a hundred million perfect is tremendously difficult. I for one reached a point years ago where writing code and drawing schematics paled; much more fun was designing systems, inventing ways to build things, and then leaving implementation details to others. I know many engineers who bailed because of boredom.

External forces intervene, too. Though age discrimination is illegal it's also a constant factor. Many 50-ish engineers will never learn Java, C++, and other new technologies. They become obsolete. Employers see this and react in not-unexpected ways. Other employers look askance at the high older engineer salaries and will consider replacing one old fart with two newbies.

Champion of Angry Programmers

SPIRE Abstract Information Overload - An IR problem  by M.Montebello

Information overload on the World-Wide Web (WWW) is a well recognised problem. Research to subdue this problem and extract maximum benefit from the Internet is still in its infancy. With huge amounts of information connected to the Internet, efficient and effective discovery of resource and knowledge has become an imminent research issue. A vast array of networks services is growing up around the Internet and massive amounts of information is added everyday. Despite the potential benefits of existing indexing, retrieving and searching techniques in assisting users in the browsing process, little has been done to ensure that the information presented is of a high recall and precision standard. Therefore, search for a specific information on this massive and exploding information resource base becomes highly critical. In this paper we discuss the issues involved in resolving the information overload over the WWW and argue that this is solely an information retrieval problem. As a contribution to the field we propose a general architecture to subdue information overload and describe how this architecture has been instantiated in a functional system we developed.

Proceedings of the String Processing and Information Retrieval: A South American Symposium
Copyright (c) 1998 Institute of Electrical and Electronics Engineers, Inc. All rights reserved.

Information overload, internet filtering agents, e-mail filtering, information filtering, user modeling, routing, ranking email

Robert M. Losee,
Minimizing Information Overload: the Ranking of Electronic Messages,
Journal of Information Science, 15, 1989, p. 179-189. Full text of article (in pdf)

Abstract:

The decision to examine a message at a particular point in time should be made rationally and economically if the message recipient is to operate efficiently. Electronic message distribution systems (e.g. email), electronic bulletin board systems, and telephone systems capable of leaving digitized voice messages (e.g., voicemail) can contribute to "information overload," defined as the economic loss associated with the examination of a number of non- or less-relevant messages, as in related information retrieval models. Our model provides a formal method for minimizing expected information overload through information filtering.

The proposed adaptive model predicts the usefulness of a message based on the available message features and may be useful to rank messages by expected importance or economic worth. The assumptions of binary and two Poisson independent probabilistic distributions of message feature frequencies are examined, and methods of incorporating these distributions into the ranking filter model are examined. Bayesian methods to incorporate user supplied relevance feedback are suggested. Analytic performance measures are proposed to predict system quality. Other message handling models, including rule based expert systems, are seen as special cases of the model. The performance is given for a set of unix shell programs which rank internet messages. Problems with the use of this formal model are examined, and areas for future research are suggested.

For additional technical discussion of this material, see Losee, Text Retrieval and Filtering: Analytic Models of Performance, Boston: Kluwer, 1998.

Losee home page at http://www.ils.unc.edu/~losee

[Feb 2,  2002]  Byte: Information Overload Fighting data asphyxiation is difficult but possible

Data is like food. A good meal is served in reasonably-sized portions from several food groups. It leaves you satisfied but not stuffed. Likewise with information, we're best served when we can partake of reasonable, useful portions, exercising discretion in what data we digest and how often we seek it out.

Unfortunately, we often do the opposite, ingesting information constantly to the point of choking on it. The risk of information asphyxiation touches all of us -- managers, Web surfers, even lazy couch tubers.

The most obvious locus of information inundation is the office: e-mail, voice mail, phone calls, meetings, business journals, faxes, memos, manuals, Web research. The list goes on. Far from bringing about the anticipated "paperless office" and reduced work load, technological innovations have increased both areas.

David Shenk, in his book Data Smog, reports that between 1980 and 1990, paper consumption in the U.S. tripled to 1,800 pounds per person. Sixty percent of the average office worker's time is spent processing paper documents. Additionally, "the typical business manager is said to read one million words per week." That's the equivalent of one and a half full-length novels per day.

Diminishing Efficiency

Information technology, in fact, often diminishes workplace efficiency. Scientific American ("Taking Computers to Task," July 1997) pointed out that despite the $1 trillion spent annually across the globe, "productivity growth measured in the seven richest nations has instead fallen precipitously in the last 30 years ... Most of the economic growth can be explained by increased employment, trade and production capacity. Computers' contributions, in contrast, nearly vanish in the noise."

Blame can be pinned on everything from sound cards to solitaire, that numbing front-desk babysitter.

Also at fault, however, is the medium and people's lack of training in how to effectively use it. When employees use e-mail to communicate with someone 50 feet away, there's a problem. Saving customer quotes in a general "user" directory is just asking for the document to become lost among hundreds of other files. Inefficient inventory software yields frustration where a simple list on paper would do the trick.

[Feb 2,  2002]  Coping With Information Overload Too much of a good thing can hurt your job performance.

[Feb 2,  2002] Corrin Weir's Dissertation Bibliography Among items:

• Edmunds, A. & Morris, A. (2000). The problem of information overload in business organisations: a review of the literature. International Journal of Information Management, 20, 17-28.
• Hall, H. (1997). Networked information: dealing with overload. Paper presented at the Information Scotland, Strathclyde Business School.
• Heylighen, F. (1999). Change and information overload: negative effects, [Online]. Available: http://pespmc1.vub.ac.be/CHINNEG.htm [2000, 16 October].
• Kerka, S. (1997). Information Management, [Online]. ERIC. Available: http://www.ericacve.org/docs/mr00009.htm [2000, 16 October].
• Lake, A. (2000). Overloaded!, [Online]. Available: http://www.flexibility.co.uk/issues/info-overloaded.htm [2000, 25 October].
• McCafferty, J. (1998). Coping with infoglut. [Online]. CFO Magazine. Available: http://www.cfopub.com/html/Articles/CFO/1998/98SEinfo.html [2000, 16 October].
• McDermott, R. & O'Dell, C. (2000). Overcoming the 'Cultural Barriers' to Sharing Knowledge, [Online]. Available: http://www.apqc.org/free/articles/km0200/index.htm [2000, 26 October].
• McMahan, K. L. (1998). Effective communication and information sharing in virtual teams, [Online]. Available: http://www.apqc.org/free/articles/km0200/index.htm [2000, 24 October].
• Meek, C. (2000). Index of links to knowledge management websites, [Online]. Available: http://www.city.grande-prairie.ab.ca/ccy_km.htm [2000, 24 October].
• Omar, M. (1997). How to deal with Information Overload on the Internet? The intelligent agent concept. [Online]. Available: http://star.arabia.com/971127/TE2.html [2000, 25 October].
• Owen, J. (2000). Coping with information overload. [Online]. Available: http://www.careerbuilder.com/wl_work_9905_overload.html [2000, 16 October].
• Van Winkle, W. (1998). Information Overload, [Online]. Computer Bits. Available: http://www.computerbits.com/archive/19980200/infoload.htm [2000, 25 October].