Slashdot Mirror

Esther Schindler writes "There was a time when programs were written in text editors. And when competition between C++ vendors was actually fierce. Step into the time travel machine as Andy Patrizio revisits the evolution and impact of the visual development metaphor. 'Visual development in its earliest stages was limited by what the PC could do. But for the IBM PC in the early 1980s, with its single-tasking operating system and 8- or 16-bit hardware, the previous software development process was text edit, compile, write down the errors, and debug with your eyes.' Where do you start? 'While TurboPascal launched the idea of an integrated development environment, [Jeff] Duntemann credits Microsoft's Visual Basic (VB), launched in 1991, with being the first real IDE.'... And yes, there's plenty more." A comment attached to the story lists two IDEs that preceded VB; can you name others?

Esther Schindler writes "If you're looking for technology to improve kitchen connectivity and home automation, you might be surprised at how little is available today. Turns out, that's a good thing. Our industry has a long history of trying to sell a solution in search of a problem. Maybe we can get away with that occasionally, when the solution is inherently fun, or when there are enough of us geeks to buy an cool-looking automated gizmo with blinking lights where a cheaper hand-held "solution" is just as good for the masses. But when it comes to home appliances, which cost a pretty penny by anyone's measure, nobody wants to invest big bucks in a "connected" device — however cool the home automation seems — where the technology platform goes away (my washing machine is 8 years old; I sure wouldn't use a PC or phone that age) or where the benefits are murky. That is, just what is it we want the kitchen automation to do? It's one thing to say, "The fridge could order food when I run out" but none of us want to scan every potato as we unload the groceries. Yet, as I wrote in Cooking up the connected kitchen, the manufacturers are paying attention to home automation and connectivity and giving your oven an app. And some of it, as I hope the article makes clear, is really cool. 'The manufacturers want to sell us technology, and we want to buy cool capabilities that actually improve the quality of our lives. What I found surprising, in my own hands-on evaluations, is how often I had a dual-stage response: "That's the dumbest thing I ever saw. (beat) Wait, I want that!"' The manufacturers are being thoughtful about both what we'd want and what we'd buy... which is something to appreciate. So what would you want from kitchen connectivity?"

Esther Schindler writes "We always talk about how programmers improve their skill by reading others' code. But the newbies aren't going to be as good at even doing that, when they start. There's some cool research underway, using eye tracking to compare how an experienced programmer looks at code compared to a novice. Seems to be early days, but worth a nod and a smile." Reader Necroman points out that if the above link is unreachable, try this one. The videos are also available on YouTube: Expert, Novice.

Esther Schindler writes "The job of dealing with an under-performing employee doesn't end when the culprit is shown the door. Everyone focuses on security tasks, after you fire the idiot, such as changing passwords, but that's just one part of the To Do list. More important, in the long run, is the cleanup job that needs to be done after you fire the turkey, looking for the hidden messes and security flaws the ex-employee may have left behind. Otherwise, you'll still be cleaning up the problems six months later."

Esther Schindler writes "Why is it that young developers imagine that older programmers can't program in a modern environment? Too many of us of a 'certain age' are facing an IT work environment that is hostile to older workers. Lately, Steven Vaughan-Nichols has been been noticing that the old meme about how grandpa can't understand iPhones, Linux, or the cloud is showing up more often even as it's becoming increasingly irrelevant. The truth is: Many older developers are every bit as good as young programmers, and he cites plenty of example of still-relevant geeks to prove it. And he writes, 'Sadly, while that should have put an end to the idea that long hours are a fact of IT life, this remnant of our factory-line past lingers both in high tech and in other industries. But what really matters is who's productive and who's not.'"

Esther Schindler writes "When Star Trek hit the air waves, talking computers were just a pipe dream. While teleportation remains elusive, several once-fictional technologies are changing the way people live and work. Here are some ways in which we're approaching the gizmos that Star Trek demonstrated. Speech recognition? Check. Holodeck? Sort of. Replicator? Workin' on it."

Esther Schindler writes "Ready for a nostalgic trip into the wayback? We had floppy disks long before we had CDs, DVDs, or USB thumb-drives. Here's the evolution of the portable media that changed everything about personal computing. 'The 8-inch drive began to show up in 1971. Since they enabled developers and users to stop using the dreaded paper tape (which were easy to fold, spindle, and mutilate, not to mention to pirate) and the loathed IBM 5081 punch card. Everyone who had ever twisted a some tape or—the horror!—dropped a deck of Hollerith cards was happy to adopt 8-inch drives. Besides, the early single-sided 8-inch floppy could hold the data of up to 3,000 punch cards, or 80K to you.'"

Esther Schindler writes "Say that you're leaving a job, either on your own volition or because they decided it was time for you to 'pursue other opportunities.' Before you leave, the HR department wants to chat with you about the employment experience, in an exit interview. 'Oh goodie,' you think. 'Now I can really tell them what I really feel.' Don't do it. If your employer couldn't find the time to ask you what was good or bad about working at the company while you were still working there, writes Lisa Vaas, why bother with honesty and potentially burned bridges now? (If they did ask, give them constructive feedback before you leave this job; they deserve it). Discuss."

Esther Schindler writes "Last year, Danny Kalev — a former member of the C++ standards committed — explained the new features in C++. Now, in C11: A New C Standard Aiming at Safer Programming, he shares an overview of the changes in C — 13 years after the ratification of the C99 standard. Kalev describes the goodies in C11, including multi-threading support, safer standard libraries, and better compliance with other industry standards."

Esther Schindler writes "Young whippersnappers might imagine that Computer Science degrees — and the term "computer science" — have been around forever. But they were invented, after all, and early programmers couldn't earn a college degree in something that hadn't been created yet. In The Evolution of the Computer Science Degree, Karen Heyman traces the history of the term and the degree, and challenges you on a geek trivia question: Which U.S. college offered the first CS degree? (It's not an obvious answer.)"

Esther Schindler writes "An MIT professor explains why "simple" ideas require hard science and how a gemstone might be the key to an optical network. As the story begins: 'For years, the dream of an all-optical network has lain somewhere between Star Wars and a paper cup and a string. Recent successful work on the creation of an optical diode is a virtual case study in both the physics and materials sciences challenges of trying to develop all-optical networks. It is also a significant step towards their final realization.' One answer may be... garnet. Yes, the January birthstone. 'The material that Ross and others in her field use is a synthetic, lab-grown garnet film. Similar to the natural mineral, often used as a gemstone, it is transparent in the infrared part of the spectrum. This makes synthetic garnet ideal for optical communications systems, which use the near infrared. Unlike natural garnet, it's also magnetic. ... While it works, it's too big and too labor intensive for use as a commercial integrated chip. For that, you need to grow garnet on silicon. The challenge that Ross's group overcame is that garnet doesn't grow on silicon.'"

Esther Schindler writes "Plenty of people want to get involved in open source, but don't know where to start. In this article, Andy Lester lists several ways to help out even if you lack confidence in your technical chops. Here are a couple of his suggestions: 'Maintenance of code and the systems surrounding the code often are neglected in the rush to create new features and to fix bugs. Look to these areas as an easy way to get your foot into a project. Most projects have a publicly visible trouble ticket system, linked from the front page of the project’s website and included in the documentation. It’s the primary conduit of communication between the users and the developers. Keeping it current is a great way to help the project. You may need to get special permissions in the ticketing system, which most project leaders will be glad to give you when you say you want to help clean up the tickets.'" What's your favorite low-profile way to contribute?

Esther Schindler writes "Many of us geeks prefer to work at home without distractions, but a lot of bosses still believe that if they don't see you, you must be lolling about, eating bon-bons and playing Angry Birds. 'There may be many reasons a manager is distrustful of telecommuting but the phenomenon of what Albiero calls "presentism"—that is, only trusting and rewarding the folks you see at their computer is a major factor.' So it may be of some use to read through the research compiled by Diann Daniel that says telecommuting creates happier and more productive employees (which naturally include fewer distractions and better work-life balance), and an accompanying infographic showing the environmental benefits from reduced commuting. She follows it up with suggestions on how managers can mentor and support teleworkers. Some of this is general advice, but some of the tips are more specific: 'It may seem like a lot more work—all this up-front addressing of communication issues that happen far more naturally in the office—but the upside is increased efficiency. Albiero sees this especially in the area of meetings. He speaks of one client who has now instituted a meeting format that is structured to allow for the first five minutes of all meetings to be "small-talk minutes." Thus, everyone knows they needn't call in for those minutes unless they want to join."

Esther Schindler writes "'Over the past century a lot of science fiction has been published, showcasing a lot of wild ideas, and if you sit enough authors at enough typewriters or word processors, somebody is bound to get a few things right. Science fiction's greater influence, though, goes beyond whether or not the authors can make a good guess,' writes Kevin J. Anderson in Science Fiction's Take on the Future of Computers: Visionaries and Imaginaries. 'Rather than predicting the future, the SF genre is much better at inspiring the future. Visionaries read or see cool ideas in their favorite SF books or films, then decide how to make it a reality.' So Anderson assembled a set of visionaries, and asked them where they thought computing is headed: Mike Resnick, Robert J. Sawyer, Greg Bear, Michael A. Stackpole, Dr. Gregory Benford, and Christopher Paolini gaze into their crystal balls. 'Forget artificial intelligence. The future of computing is artificial consciousness, and it will be here within 20 years, and maybe much sooner than that,' says Sawyer. 'Our future wired world will have smart, wireless robots — gofers in hospitals, security guards with IR vision at night, lawn mowers, etc. We ourselves will be wired, with devices and embedded sensors taking in data and giving it out — a two way street,' contributes Benford."

Esther Schindler writes "In this interview with Steven Vaughan-Nichols, Linus Torvalds shares hard-won wisdom about managing software development projects, including encouraging community involvement, the importance of programming tools, and ensuring the project stays on track. For instance, regarding getting people to contribute to your project, he says, 'If you start off with some "kumba-ya feeling" where you think people from all the world are going to come together to make a better world by working together on your project, you probably won't be going very far.'"

Esther Schindler writes "With the Xeon 7600 line, Intel is finally using the 'R' word: RISC. With the new chips, Intel is targeting the mission-critical market dominated by Sun SPARC and IBM Power, a first. Can the Xeon E7 processor deliver Intel's final blow to the RISC market, which includes its own Itanium? 'With the launch of the E7 earlier this year, it seemed Intel was finally ready to make its final push, calling out RISC by name. "The days of IT organizations being forced to deploy expensive, closed RISC architectures for mission-critical applications are nearing an end," said Kirk Skaugen, vice president and general manager of Intel's Data Center Group, in a statement announcing the E7 line. Bold words.' Andy Patrizio interviews several experts; what do you think?"

Esther Schindler writes "Every mobile device you own has its own power supply and its own proprietary plug. There oughta be a better way, says Alfred Poor. Fortunately, he reports, the IEEE is coming to the rescue. "Their Universal Power Adapter for Mobile Devices (UPAMD) Working Group is developing a new standard that will not just address the needs of laptops and tablets, but will be intended to work with just about any electronics device that required between 10 and 240 watts of power," Poor writes. It's about darned time." If there's one thing I wish for all laptop power supplies, it's that they would license from Apple (or work around, patent-wise) the magnet attachment system that makes cable-tripping far less dangerous to man or beast, compared to a few years ago.

Esther Schindler writes "It's been 13 years since the first iteration of the C++ language. Danny Kalev, a former member of the C++ standards committee, explains how the programming language has been improved and how it can help you write better code."

Esther Schindler writes "Feeling a little overwhelmed by changing web standards and new browser choices? You aren't the only one. Mozilla is launching development tracks for the next two editions of its Firefox Web browser immediately, with hopes to push both into general release before the end of the year. This while Microsoft previews Internet Explorer 10 on the heels of its IE9 release, and Google projects Chrome 13 just one year after Chrome 7. Meanwhile, HTML5, the next version of the Web's primary language, appears to have entered a permanent gestation phase. Writes Scott Fulton: All the confusion has prompted Web developers to ask this question: What do we develop our sites against now?"

Esther Schindler writes "'Who has money to train these guys nowadays? They should be lucky they're still employed, right? Keep thinking that way,' writes Lisa Vaas. The competition applauds your choice to glue your wallet shut. Or, to put this another way: This is why the boss won't pay for developer training. Vaas explains how those still training manage to get their training budgets funded."

Esther Schindler writes "Does the computer industry seem just a little too strange? Never fear: Monty Python encapsulated several nuggets of wisdom years ago that summarize exactly what is behind the sometimes-tawdry behavior of vendors, the open source community, and marketing departments."

Esther Schindler writes "After a lengthy gestation period, the third generation of the Universal Serial Bus is making its way to the market. USB 3.0, also known as SuperSpeed USB, has throughput of up to 5 gigabits per second. That's even faster than the 3Gb/sec of SATA hard drives and 1Gb/sec of high-end networking in the home. USB 3.0: Everything You Need to Know goes into plenty of the techie details. But is it already obsolete — will LightPeak make USB 3.0 irrelevant?"

Esther Schindler writes "After several years of trying, graphics processing units (GPUs) are beginning to win over the major server vendors. Dell and IBM are the first tier-one server vendors to adopt GPUs as server processors for high-performance computing (HPC). Here's a high level view of the hardware change and what it might mean to your data center. (Hint: faster servers.) The article also addresses what it takes to write software for GPUs: 'Adopting GPU computing is not a drop-in task. You can't just add a few boards and let the processors do the rest, as when you add more CPUs. Some programming work has to be done, and it's not something that can be accomplished with a few libraries and lines of code.'"

Esther Schindler writes "'Scalability' isn't a checkbox on a vendor's feature chart — though plenty of them speak of it that way. In this IT Expert Voice article, Scott Fulton examines how we define 'scalability,' why it's data that has to scale more than servers, and how old architectural models don't always apply. He writes, 'If you believe that a scalable architecture for an information system, by definition, gives you more output in proportion to the resources you throw at it, then you may be thinking a cloud-based deployment could give your existing system "infinite scalability." Companies that are trying out that theory for the first time are discovering not just that the theory is flawed, but that their systems are flawed and now they're calling out for help.'"

Esther Schindler writes "We like to imagine that every Microsoft OS installation will work just as well as the company promises. When things don't work out, identifying and remedying the case of failure can be time-consuming and frustrating. This lesson in how to determine why Windows 7 didn't install may help you troubleshoot a problem of your own, and save you from a Lost Weekend. Maybe you'll find this account useful all on its own. But the real key here is that the author is Ed Tittel — who's written over 100 books. If this hardware geek spends days solving a CPU-meets-Windows 7 problem, what chance do mere mortals have?"

Esther Schindler writes "It's easy for techies to enumerate the reasons that Internet Explorer 6 should die. Although the percentage of users who use IE6 has dropped to about 12%, many web developers are forced to make sure their websites work with the ancient browser (which presents additional problems, such as keeping their companies from upgrading to newer versions of Windows). But rather than indulge in an emotional rant, in 'Why You Can't Pry IE6 Out Of Their Cold Dead Hands,' I set about to find out why the companies that remain standardized on IE6 haven't upgraded (never mind to what). In short: user and business-owner ignorance and/or disinterest in new technology; being stuck with a critical business app that relies on IE6; finding a budget to update internal IE6 apps that will work the same as they used to; and keeping users away from newer Web 2.0 sites."

Esther Schindler writes "According to this article at IT Expert Voice, Windows 7 and IPv6: Useful at Last?, we've had so many predictions that this will be 'the year of IPv6' that most of us have stopped listening. But the network protocol may have new life breathed into it because IPv6 is a requirement for DirectAccess. DirectAccess, a feature in Windows 7, makes remote access a lot easier — and it doesn't require a VPN. (Lisa Vaas interviews security experts and network admins to find out what they think of that idea.) The two articles examine the advantages and disadvantages of DirectAccess, with particular attention to the possibility that Microsoft's sponsorship may give IPv6 the deployment push it has lacked."

Esther Schindler writes "The Airline Control Program (ACP), introduced by IBM around 1967, predated the term 'open source' by decades. But you may be surprised by how much of its development resembles the FOSS movement today. The ITWorld.com article An Abbreviated History of ACP, One of the Oldest Open Source Applications describes what made it special."

Esther Schindler writes "Those hours you spent rolling dice in your youth weren't wasted according to my 10 Business Lessons I Learned from Playing Dungeons & Dragons. Playing fantasy role playing games did more than teach the rules of combat or proper behavior in a dragon's lair. D&D can instruct you in several skills that can help your career. Such as: 'One spell, used well, can be more powerful than an entire book full of spells' and 'It's better to out-smart an orc than to fight one.'" What other wisdom have you gained from your time sequestered with various RPGs?

Esther Schindler writes "Does your favorite open source project need just a little extra functionality? As Esther Schindler explains in this IT World article, your company can encourage the developers to add the features you've been yearning for — for far, far less money than you imagine. She interviews companies who have sponsored 'code-a-thons' for Drupal, Plone, simwiddy, and a set of applications for British Telecom, and provides specific pointers. From the article: 'To ensure that the event happens and that it meets its goals, you must connect with the right members of the community and motivate them to work with you. "It's not like these people are paid to work for your interests," points out Brightcove's Whatcott. If your business already has project committers on its staff, then it's just a matter of leveraging existing relationships. But, says Stahl, "Someone less 'core' in the community might well have a harder time.'"'

Esther Schindler writes "Several weeks ago, Lynn Greiner's article on the state of the scripting universe was slashdotted. Several people raised their eyebrows at the (to them) obvious omissions, since the article only covered PHP, Perl, Python, Ruby, Tcl and JavaScript. As I wrote at the time, Lynn chose those languages because hers was a follow-up to an article from three years back. However, it was a fair point. While CIO has covered several in depth, those five dynamic languages are not the only ones developers use. In 6 Scripting Languages Your Developers Wish You'd Let Them Use, CIO looks at several (including Groovy, Scala, Lua, F#, Clojure and Boo) which deserve more attention for business software development, even if your shop is dedicated to Java or .NET. Each language gets a formal definition and then a quote or two from a developer who explains why it inspires passion."

Esther Schindler writes to tell us that Lynn Greiner has another look at the state of the scripting universe as a follow on to the same topic three years ago. Greiner talks to major players from each of the main scripting languages (PHP, Perl, Tcl, Python, Ruby, and Javascript) to find out the current status and where they are headed in the future. "The biggest change since 2005 has been the growth of richer Web applications that perform more of their computations in the browser using JavaScript. The demand for these applications has forced developers to learn and use JavaScript much more than before. There's also been a lot of interest in Ruby, another dynamic language, spurred by the release and growth of Ruby on Rails. As a result of these changes, many developers are becoming more comfortable with dynamic languages."

Esther Schindler writes "Finally, a Forrester analyst who understands the attitudes of software developers. Mike Gualtieri identifies nine behaviors managers need to steer clear of or risk being labeled 'clueless' — from control freak tendencies to being a vendor puppet. My favorite, however, is point #8: 'the CIO collaborates to death,' in which Gualtieri opines, 'And, if you never watched Star Trek then you shouldn't even be a CIO.'"

Esther Schindler writes "Do you use SOAP, CORBA or EJBs? You might want to take a look at Etch, writes James Turner for CIO.com. It's language-, platform- and transport-agnostic, and Cisco is planning to release it as open source. Certainly, it offers some technical benefits: 'In addition to a simplified configuration, Etch also promises less overhead over the wire, compared to SOAP. In a testbed environment where SOAP was managing around 900 calls a second, Etch generated more than 50,000 messages in a one-way mode, and 15,000 transactions with a full round-trip, company officials stated.' And the open source part? Cisco is in the process of deciding what license to use. 'The intent is to use a less restrictive license than GPL, perhaps Apache or Mozilla. This is to allow commercial developers to incorporate Etch into products without licensing issues. A final announcement on the licensing decision will be available in the next month.'"

Esther Schindler writes "CSO has an annotated, zoomable map of real botnet topologies showing the interconnections between the compromised computers and the command-and-control systems that direct them. The map is based on work by security researcher David Voreland; it has interactive controls so you can zoom in and explore botnets' inner workings. Hackers use botnets for spamming, DDoS attacks and identity theft. One recent example is the Storm botnet, which may have comprised 1 million or more zombie systems at its peak. As with any networking challenge, there are good (resilient) designs and some not-so-good ones. In some cases the topology may be indicative of a particular botnet's purpose, or of a herder on the run."

Esther Schindler sends a note about two journalists for very different publications (herself one of them) urging IBM to open-source, not all of OS/2 — they've consistently refused to do that — but instead one of its most powerful features: SOM, the System Object Model. Steven J. Vaughan-Nichols writes at desktoplinux.com, "IBM, I'm told by developers who should know, still has all of SOM's source code and it all belongs to IBM. It's because IBM doesn't have all the code for OS/2 and some of it belongs to Microsoft that IBM open-sourcing OS/2 has proven to be a futile hope." And Esther Schindler takes the developer angle in a blog post at CIO.com: "Could the open-source community use a library packaging technology that enables languages to share class libraries regardless of the language an application was written in? I dare say it could, especially since the code to accomplish that goal was written (and shelved) more than ten years ago. All it takes to make that code available is to ask IBM to release SOM and DSOM as open-source." What are the business issues that would convince IBM to assent?

Esther Schindler writes "Developers spend a lot of time telling managers, 'Let me use the tool that's appropriate for the job' (cue the '...everything looks like a nail' meme here). But rarely do we enumerate when a language is the right one for a particular job, and when it's a very, very wrong choice. James Turner, writing for CIO.com, identifies five tasks for which perl is ideally suited, and four that... well, really, shouldn't you choose something else? This is the first article in a series that will examine what each language is good at, and for which tasks it's just plain dumb. Another article is coming RSN about JavaScript, and yet another for PHP... with more promised, should these first articles do well."

Esther Schindler writes to mention that one IT leader who came from big business found himself in quite another world when he transitioned into a smaller business, specifically with respect to the amount of attention from their vendors. He presents an amusing approach with a familiar twist. "Not only are the IBMs of the world leaving money on the table, they're also risking future sales. The IT leaders at small organizations will in many cases be employed by larger organizations someday. Why alienate them? Vendors could engage IT leaders in small organizations now and build brand loyalty. How could they make such a business model work? Let's imagine (with apologies to George Lucas) what Yoda might do if he were running a large consultancy."

Esther Schindler writes "Every year, there's some retailer whose e-commerce or supply chain fails. And it's a big deal, since the holiday shopping season can make or break their year. The IT challenge encompasses everything from server scalability to supply chain management to search engine optimization to database cajoling to business integration to... well, come to think of it, just about everything. To explore this, CIO.com has a big package of articles examining "Black Friday" and its implications, entitled E-Commerce and Supply Chain Systems Gird for Black Friday. Topics covered include online shopping and holiday IT failures. Despite all this—and at least ten years of industry experience in e-commerce sales—we all just know that someone will make yet another big mistake. I wonder who it'll be this year?"

Esther Schindler writes "Sure, everyone uses technology on the job. But you may not have contemplated the tools used by paranormal investigators (at least, not until you began thinking about Halloween) who look for the truth in ghosts and other things that go Bump in the Night. In Paranormal Investigations and Technology: Where Ghosts and Gadgets Meet, CIO's Al Sacco writes about the most unusual of tool chests, with everything from thermometers to blimp cams." You want spooky? An anonymous reader passed a link to a survey that says a third of Americans believe in ghosts. Who you gonna call?

Esther Schindler writes "Some products just didn't deserve to die. But they did, because the companies made bad business decisions. Dearly Departed, revisits several favorites — from minicomputers to software utilities — and mourns the best and brightest that died an untimely death. What companies or products would you add? Which of them deserved to go?"

Esther Schindler writes "Often, the difference between the success and failure of any IT project is spotting critical early warning signs that the project is in trouble. CIO.com offers a few ways to identify the symptoms, as well as suggestions about what you can do to fix a project gone wrong. ' The original study (which is still sometimes quoted as if it were current) was shocking. In 1994, the researchers found that 31 percent of the IT projects were flat failures. That is, they were abandoned before completion and produced nothing useful. Only about 16 percent of all projects were completely successful: delivering applications on time, within budget and with all the originally specified features. "As of 2006, the absolute failure rate is down to 19 percent," Johnson says. "The success rate is up to 35 percent." The remaining 46 percent are what the Standish Group calls "challenged": projects that didn't meet the criteria for total success but delivered a useful product.'"

Esther Schindler writes "Database decisions are never easy, even — or maybe especially — when one choice is extremely popular. To highlight the advantages and disadvantages of the open-source MySQL DBMS, CIO.com asked two open-source experts to enumerate the reasons to choose MySQL and to pick something else. Tina Gasperson takes the 5 reasons to use MySQL side, and Brent Toderash discusses 8 reasons not to. Note that this isn't an 'open source vs proprietary databases' comparison; it's about MySQL's suitability in enterprise situations."

Esther Schindler writes "CSO Magazine has an article about "The Scourge of Image Spam," with an explanation of its effect (a year ago, fewer than five out of 100 e-mails were image spam; today, up to 40 percent are in that category, and image spam is the reason spam traffic overall doubled in 2006). You might already know about that, ho-hum. But what's even cooler is a interactive graphic page which demonstrates the various methods used by image spammers and how it works."

Esther Schindler writes "An article on CIO.com presents input from several telecommuting IT professionals about the benefits that working from home brings to the enterprise. They suggest some processes that help remote workers interact with other team members, and discuss the irritations that twist telecommuters' shorts in a knot. In short, it's what employees truly want the boss to know about telecommuting. Two sidebars also discuss tips for telecommuters who don't want their careers to stall because they're 'out of sight, out of mind,' and the out of pocket expenses that the company and telecommuter need to divvy up."

Esther Schindler writes "Not just another 'why big companies should adopt Macs' article, CIO is running a piece assuming that Macs are already on the way in the door. Hi, I'm a Mac, and I'm Your Enterprise Computer offers advice to IT managers about how to integrate Apple systems into the existing IT infrastructure, and offers hints from leading Mac OS X experts on configuring those systems once they've arrived. '[A] key element in corporate Macintosh adoption is the importance of third-party software and custom solutions. They can help smooth the way for integrating Macs onto the network. While specialists say they wish third-party support were greater, the openness of the Mac makes correcting issues possible. Don't discount the lure of the well-worn path that draws and then traps your IT staff into familiar habits.'"

Esther Schindler writes "Sysadmins and email administrators were asked to identify the one thing they wish the CIO understood about their efforts to fight spam. The CIO website is now running their five most important tips, in an effort to educate the corporate brass. Recommendations are mostly along the lines of informing corporate management; letting bosses know that there is no 'silver bullet', and that the battle will never really end. There's also a suggestion to educate on technical matters, bringing executives into the loop on terms like SMTP and POP. Their first recommendation, though, is to make sure no mail is lost. 'This is a risk management practice, and you need to decide where you want to put your risk. Would you rather risk getting spam with lower risk of losing/delaying messages you actually wanted to get, or would you rather risk losing/delaying legitimate messages with lower risk of spam? You can't have both, no matter how loudly you scream.'"