Skip to main content

Nielsen Sounds Off on Web Design

Jakob Nielsen sounds off on better web design. Interestingly enough, he doesn't mention blogs per say but he does the goal is to limit what needs to be in an email from a corporate standpoint. If you believe that concept, run, don't walk and pick up the Simplicity Handbook (http://www.simplerwork.com/handbook.htm) because Bill Jensen suggests deleting 75% of your new email as a way to become more productive. Funnily enough, the approach actually works. Bill also has great ideas for making your emails more effective.
 
Now, who's to say how Nielsen regards RSS feeds but the fact is, using something like NewsGator (which makes new blog posts appear as emails), it simply makes it an easier search mechanism (especially when combined with Lookout).
 
Sadly, the issue with making intranets more useful is NOT having more intranets - the problem I have found is with the people. That's why blogs and wikis are so valuable. I can easily find out what people are up to by reading their blogs. No blog? I don't want to read a status report (ugh!). Nielsen may be good at saying what's wrong - but he needs to give better insight into why people don't use intranets. (hint: It's NOT because of PDFs,popups and searches - it's because they don't want to have to go somewhere else).
 

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...