An employer can save more than $11,000 per employee when that person works from home even half the time, according to FlexJobs. Meanwhile, a typical telecommuter saves anywhere from $2,000 to $7,000 a year on expenses like transportation and clothing.
Savings from working at home
Savings from working at home
An employer can save more than $11,000 per employee when that person works from home even half the time, according to FlexJobs. Meanwhile, a typical telecommuter saves anywhere from $2,000 to $7,000 a year on expenses like transportation and clothing.
Savings from working at home
Savings from working at home
An employer can save more than $11,000 per employee when that person works from home even half the time, according to FlexJobs. Meanwhile, a typical telecommuter saves anywhere from $2,000 to $7,000 a year on expenses like transportation and clothing.
Savings from working at home
The never ending game of "Business Alignment"
On top of that, the second issue is that there’s this new technology base, and a new application set…I call this a different circus with different clowns. And you’ve got CIOs who have done a good job of getting us this far at the tail end of a maturity curve. Their challenge is whether these buttoned down, slack eliminating, control oriented IT leaderships and providers can morph into a very different type of role.
The never ending game of "Business Alignment"
On top of that, the second issue is that there’s this new technology base, and a new application set…I call this a different circus with different clowns. And you’ve got CIOs who have done a good job of getting us this far at the tail end of a maturity curve. Their challenge is whether these buttoned down, slack eliminating, control oriented IT leaderships and providers can morph into a very different type of role.
The never ending game of "Business Alignment"
On top of that, the second issue is that there’s this new technology base, and a new application set…I call this a different circus with different clowns. And you’ve got CIOs who have done a good job of getting us this far at the tail end of a maturity curve. Their challenge is whether these buttoned down, slack eliminating, control oriented IT leaderships and providers can morph into a very different type of role.
The seven layer ROBO attack
At the branch office what the industry has done is stack up appliances for everything from unified communications to WAN optimization, firewalls, routers, wireless network controllers, etc., so if you have 10,000 offices and four appliances per, you have 40,000 appliances spread all over the place. So what this one says is, “We want to integrate all those branch appliances in software and be able to control the bandwidth to those branch offices a lot more effectively and efficiently.
The seven layer ROBO attack
At the branch office what the industry has done is stack up appliances for everything from unified communications to WAN optimization, firewalls, routers, wireless network controllers, etc., so if you have 10,000 offices and four appliances per, you have 40,000 appliances spread all over the place. So what this one says is, “We want to integrate all those branch appliances in software and be able to control the bandwidth to those branch offices a lot more effectively and efficiently.
The seven layer ROBO attack
At the branch office what the industry has done is stack up appliances for everything from unified communications to WAN optimization, firewalls, routers, wireless network controllers, etc., so if you have 10,000 offices and four appliances per, you have 40,000 appliances spread all over the place. So what this one says is, “We want to integrate all those branch appliances in software and be able to control the bandwidth to those branch offices a lot more effectively and efficiently.
Things were different back in 2003, but developers still were kingmakers
From Rachel Chalmer’s 2003, coverage of Novell buying “SuSE” (451 client access required):
Historically, Novell’s Achilles’ heel has been its inability to keep its independent developer community happy. Some fled NetWare for OS/2, which IBM botched in its turn. Meanwhile, Microsoft was happy to embrace and pamper NetWare and OS/2 burn victims as independent software vendors for Windows. Now developers are asking themselves whether Novell has learned its lesson, or whether it’s about to make the same mistake again.