Print

Short Takes: March 1, 2009



Email
March 2, 2009 —  (Page 1 of 2)
Take a time out to be sick
Whatever happened to the sick day? As someone who works from home, I've noticed that the sick day has no meaning here. When I came down with pneumonia in February, I had to take a day off. But I ended up working anyway because I had some phone calls scheduled that day, and I couldn't help but check my e-mail. Even my sideline jobs, freelancing for other magazines, couldn't be put off.

Everything in our digital culture screams “Now! Now! Now!” When someone is down with an illness, nothing else stops or slows down. It's as if the modern world can't accept our humanity at times. Maybe the next time I get ill, I'll unplug my DSL router and take the battery out of my phone, because as I write this, almost a week after I first became ill, I am still sick. No rest for the wired. — Alex Handy

Another doomed UAC?
After Windows Vista improved Windows security, it was disappointing that the Windows 7 beta backslid.

Two serious vulnerabilities were uncovered in User Account Control (UAC) by Windows bloggers Rafael Rivera and Long Zheng, and Microsoft's initial response was not encouraging. The company downplayed the vulnerabilities, arguing that its priority was to make UAC more user friendly (perhaps its engineers watched too many Apple ads).

Microsoft recouped my confidence when it announced that it would modify Windows to run UAC's control panel in a high-integrity process. That eliminates the capacity for malware to manipulate UAC, because the malware would first have to elevate its privileges in order to do so. I just wonder why wasn't this done to begin with back when UAC first shipped? — David Worthington

Test away that 90%
It is said that the first half of a software project takes 90% of the time, and the second half takes the other 90%. A big part of that reason is because of incorrect, incomplete or incoherent requirements. In a webinar I hosted last week, Gary Mogyorodi, president of the Canadian Software Testing Board, discussed the two keys points necessary to convert your development team to the method called requirements-based testing—ambiguity reviews and cause-effect graphing.



Related Search Term(s): Short takes

Pages 1 2 


Share this link: http://sdt.bz/33307
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Short Takes: July 1, 2010
The editors talk about Apple fatigue, TechEd and putting your face in space Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
MAY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Creation
To write better software, cultivate your ability to be creative.
05/19/2012 07:40 PM EST

Slick...but who needs it?
compilr.com is a well-designed site and the folks behind it seem to have their heart in the right place. But...who needs it?
05/16/2012 12:45 PM EST

How to be a better software developer
Want to be a better developer? You won't get there by mastering an interesting language or learning a new set of APIs.
05/14/2012 12:18 PM EST

Wooing Galatea
Do yourself a favor and check out Galatea 2.2, a wonderful book by novelist Richard Powers.
05/12/2012 07:05 PM EST

The world as story
An artificial-intelligence system at Carnegie Mellon seeks to understand the world by making statements about it.
05/10/2012 06:39 AM EST

The Rise of the Brogrammer, or the Rise of the Sexist Programmer?
Women in Silicon Valley get vocal about sexist ads and campaigns that contribute to a tense work environment.
05/09/2012 03:14 PM EST

 

Events calendar tab
5/23/2012 to 5/24/2012
Chicago
IEG

6/3/2012 to 6/7/2012
Orlando
IBM Rational

6/10/2012 to 6/15/2012
Las Vegas
SQE

6/10/2012 to 6/15/2012
Las Vegas
SQE

6/11/2012 to 6/14/2012
Bellevue, Wash.
AMD