Here are some interesting comments I’ve read in the past couple of months in technical trade magazines:
- Some users hate choice and flexibility, and by giving it to them, you are simply increasing the amount of mistakes they will make and the IT time and resources they will consume. -eWeek
- If given a choice, our end users will always choose ease of use over better security. -VeriSign chairman & CEO
- Ease of Use Equals Use -Software Development
- In the world of Google, blogs, e-mail and IM, identity is the collection of places you go. Opportunity flag: Currently, managing these identity trails is a difficult, often-ignored task. -eWeek (both)
- RSS is well-suited to replace e-mail in workgroups whose members must communicate frequently. -Brian Livingston
- The key to a successful development project is to manage your own expectations. -Chad Dickerson
- We all lose more brilliant ideas than we express. Our minds are too busy coping with constant sensory bombardment. -Tom Yager
- Quite simply, the Google philosophy can be expressed in five general principles: Work on things that matter, affect everyone in the world, solve problems with algorithms if possible [i.e. automate what you can], hire bright people and give them lots of freedom, and don’t be afraid to try new things. As a general practice, Google also requires that its engineers spend 20 percent of their time working on personal technology projects unrelated to their primary projects. -InfoWorld
- Visualization, annotation and socialization are becoming must-have features in applications. If they’re missing from yours, you could be producing a non-starter. -Collaboration’ new age
- FC81: It’s a blog world after all, If it’ urgent, ignore it and Things leaders do
Winter is over and spring is finally here to stay. So, I thought it was time to drop the use of cool colors for something a bit sunnier. So I turned to Color Wheel Pro for my new color palette. I actually like its Sunny palette; so, that’s what I based my new color scheme upon. Does it work for you? I also played around with how I handle links. My goal is to be more subtle while still informing you of potential actions while you’re here. Does it work for you? As with any change of this sort, some will like it while others won’t. Feedback from both perspectives is always welcome. What would you do differently and why? Thanks in advance.
The following logic seems to be more prevalent these days: if something is wrong but someone else does something worse, then what I’m doing isn’t so bad. The actions of others don’t excuse my own. My environment doesn’t prevent me from making the right choices either–granted some environments are more difficult than others. Choice is not free; it always has a cost–not that cost has to be bad. If choice were free, what would be the point of choosing? Need some practical examples? I only downloaded one song, one album, one… I was only driving five miles over the speed limit… I was only in the car pool lane for five minutes…
(Part 4, Part 3, Part 2, Part 1)
Potential issues/challenges/opportunities to be aware in developing a managed add-in for Office:
From the aggregator mailbag:
- Chris Anderson finds that MVC often leads to over-architected applications.
- Hopefully we’ll see continued enhancement to Adam Natha’s CLR SPY tool. As someone who already relies on FxCop‘s static analysis, I’m interested in CLR SPY’s dynamic analysis support. Speaking of revisions to software, FxCop is due for one.
- Dare posts his RSS Bandit TODO list.
- Jason Bock’s reusable .NET Error Dialog received some discussion.
- Chris Pratley talks about the Watson approach to software quality (i.e. let’s measure it). More importantly, Microsoft offers Watson data freely for anyone writing applications on Windows. Chris continues to explore the following counter-intuitive concept, here: The goal is to ship a product with the highest known quality, not necessarily with fewer bugs.
- John Lam reminds us that code coverage tells us only about faults of commission, not faults of omission. He’s also been having fun with the Shadows & Highlights feature in Photoshop CS.
(Part 3, Part 2, Part 1)
Concerning Microsoft .NET:
- PAG‘s Application Updater Block how-to (original) update was discussed–although I cannot access the actual update referenced here. Another good article on the Background Intelligent Transfer Service (BITS) can be found here.
- The Global Assembly Cache (GAC) was demystified.
- Garbage collection and finalization were discussed by Eric Gunnerson and Larry O’Brien (and others) a fair amount (, , , *, , , , , , , ). Chris Brumme weighed in (!) on finalization, too.
- Longhorn’s XAML received a fair bit of coverage (, *, ,  – With Longhorn we are doubling down on OLE compound files to have a good way to have complex documents with rich metadata., , ).