Deleting comments in blogspot isn’t as intuitive as deleting a comment in say, wordpress. One more thing, you can’t edit a comment already published in blogspot, the only course of action you are have is to either accept or delete the comment. Here’s the instruction which I figured out my own how to delete a comment in blogspot:

1. Sign in to your blog.
2. Click the comments link located at the bottom of your post.
3. Comment trail appears. You can see located at the lower portion of the comment is a gray trash can icon. If you want to delete this comment, click the trash can icon.
4. Confirmation message appears. Click ok to confirm.

Sometimes, your project would require you to have two web servers running in your local computer or your development environment. In cases like this, you need to specify different port numbers to web servers like Apache and IIS to avoid conflict. The default port number of web server is port 80. You need to change this number ine one of your web servers in order to make the two web servers work concurrently.

If you decide to change the port number of IIS in Windows XP, it’s easy.

1. Click the Start Button -> Control Panel -> Administrative Tools -> Internet Information Service.
2. IIS Manager opens. In the left side of the panel, click Web Sites -> Default Web Sites.
   Right click Default Web Sites and click Properties.
3. Properties Dialog opens. Look for the Web Site Tab. Under Web Site Tab, change the port number from the default port number 80 to say, for example 8000. Be careful in replacing the port number because there are port numbers that are already pre-assigned to other services (SQL Server is port number 1433, mail is port 25 etc).
4. Click Ok and exit.
   
   To access this server, simply type in the web address of the browser
   
   http:\localhost:8000\
   
   Where 8000 is the port number you indicated.
   
   On the other hand, if you want to change the port number of Apache web server instead of the IIS, follow this instruction:

1. 1. Look for the file httpd.conf in the Apache folder. (Do a search if you have hard time finding where the Apache folder was installed). If you’re using XAMPP, its under the c:\xampp\apache\conf directory.
2. Open the httpd.conf using Notepad.
3. In the file, find the following section:
   
   
   ## Listen: Allows you to bind Apache to specific IP addresses and/or
   # ports, instead of the default. See also the
   # directive.
   ## Change this to Listen on specific IP addresses as shown below to
   # prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
   ##Listen 12.34.56.78:80
   Listen 80
   
4. Simply change the number after the word Listen to the port you want it to use, say for example, port 8020.
5. Save the file and restart Apache. To restart Apache using the XAMPP control panel, simply click the Stop and when it stops, click Start.

Be aware though that you will have to reconfigure any firewalls and routers to forward requests to your new port. Also, some people may have problems accessing your website if it is not on port 80 or the alternative 8080.

Looking for the coolest jobs in IT? A new survey of information technology and network security specialists suggests that the place to look is on the front lines of cyberspace — and that the variety of work is greater than many might suspect.

The survey was conducted by the SANS Institute, the IT security training and research organization. The results will be published later this year in the form of an information booklet aimed at interesting students to consider a career in IT security.

The institute asked information security practitioners in government and non-government positions to describe their jobs and the most interesting aspects about working in them. It also asked security specialists to select which jobs they thought were “very cool.”

The top-ranking “coolest” IT security jobs according to government security employees:

1. Information security crime investigator or forensics expert.
Why it’s cool: “The thrill of the hunt! You never encounter the same crime twice!”

2. System, network or web penetration tester.
Why it’s cool: “You can be a hacker, but do it legally and get paid a lot of money!” “The power to understand how systems can be penetrated and misused is something less than 1 percent of people in the entire security industry know, let alone the average citizen.”

3. Forensics analyst
Why it’s cool: “It’s CSI for cyber geeks!” “It’s like being one of the good spies on James Bond.” “Trying to find evidence without altering the system and maintaining the chain of evidence is challenging.”

4. (Tie) Incident response, incident handler
Why it’s cool: “This may be the top of the ‘top gun’ jobs because it lets you move into a cooler, analytical environment where you can go deep with your knowledge.” “You get visibility with your organization when they happen.” “Like the secret agent of tech geekdom.”

4. (Tie) Security architect
Why it’s cool: “You get to design the solution, and not just for the perimeter.” “You get to work with all the tech experts as a team, to plan the technology directions.” “You get to research and play with new ‘toys’ all the time.”

6. Vulnerability researcher
Why it’s cool: “You get to tear apart malware and find out how it ticks.” “Reverse engineers take a deep look into code segments to determine what is really happening under the hood.” “It’s a very exclusive club.”

7. (Tie) Network security engineer
Why it’s cool: “If there’s one person indispensable, it’s the network person.” “This is where the action is and where everything is in a state of flux with newer and newer technology.”

7. (Tie) Security analyst
Why it’s cool: “This job has influence at the top of the organization.” “If you want to make a difference but don’t necessarily want all the managerial BS, this is the job for you.” “It is the only clear path to the real top gun of security: chief information security officer.”

7. (Tie) Sworn law enforcement officer specializing in information security crime
Why it’s cool: “Ability to catch the bad guys … the end result is a rush.” “This is where the geeks among us can really show up the jocks.” “Security specialist and you get to carry a gun!”

10. (Tie) CISO/ISO or director of securityWhy it’s cool: “I can get a lot done with little to no push back.” “You get to decide where to build the ‘watch towers,’ how many rangers are stationed in the park, where fires can be safely built, and the rules of engagement.”

10. (Tie) Application penetration testerWhy it’s cool: “You’re an ‘ethical hacker.’” “It takes equal parts technical ability and creativity,” “Combines applying different thought processes to system analysis with exploration tools, and a sort of dangerous level of knowledge.”

Want to make more money as an enterprise application developer? You’re in luck–if you know open source.

Enterprises increasingly deploy open-source software, and look to specialized application development on top of it, to drive business value:

The rise of open-source software in application development puts developers with a specialization in those technologies in a position to ask for a 30 (percent) or 40 percent pay increase, Kirven says. “We’ve gotten more requests from our permanent-placement division for open-source developers in the last six months than in the last five or six years combined,” he says. “It’s not as easy as getting free software; someone has to get it up and running. LAMP is everywhere now–these types of technologies no one heard of 18 months ago are all the sudden becoming a hot commodity.”

Indeed. Not only does open source bring developers more money, but it also apparently brings them more satisfaction.

Jon Williams, chief technology officer of test preparation company Kaplan, made it very that open source is one of his best retention tools.

Let people do interesting work, and they stick around. Make them mindlessly monitor that Windows machine, and they’ll bolt.

6. Asking for the Same Info Twice
Users shouldn’t have to enter the same information more than once. After all, computers are pretty good at remembering data. The only reason users have to repeat themselves is because programmers get lazy and don’t transfer the answers from one part of the app to another.

7. No Default Values
Defaults help users in many ways. Most importantly, defaults can: speed up the interaction by freeing users from having to specify a value if the default is acceptable; teach, by example, the type of answer that is appropriate for the question; and direct novice users toward a safe or common outcome, by letting them accept the default if they don’t know what else to do.

Because I used Liste Rouge Paris as a bad example under Mistake #1a, I thought I’d play nice and use them as a good example here. The tailor offers 15 different collar styles (among many other options) for people ordering custom-designed shirts. Luckily, they also provide good defaults for each of the many choices. In testing, this proved helpful to our first-time user, because the defaults steered him toward the most common or appropriate options when he didn’t have a particular preference.

Dialog to specify your shirt’s collar on www.listerouge-paris.com (3 of 15 styles shown).

8. Dumping Users into the App
Most Web-based applications are ephemeral applications that users encounter as a by-product of their surfing. Even if users deliberately seek out a new app, they often approach it without a conceptual model of how it works. People don’t know the workflow or the steps, they don’t know the expected outcome, and they don’t know the basic concepts that they’ll be manipulating. For traditional applications, this is less of a problem. Even if someone has never used PowerPoint, they’ve probably seen a slide presentation. Thus, a new PowerPoint user will typically have at least a bare-bones understanding of the application before double-clicking the icon for the first time.

For mission-critical applications, you can often assume that most users have tried the app many times before. You can also often assume that new users will get some training before seeing the UI on their own. At the minimum, they’ll usually have nearby colleagues who can give them a few pointers on the basics. And a good boss will give new hires some background info as to why they’re being asked to use the application and what they’re supposed to accomplish with it. Sadly, none of these aides to understanding apply for most Web-based applications. They don’t even apply for many ephemeral intranet applications.

Usability suffers when users are dumped directly into an application’s guts without any set-up to give them an idea of what’s going to happen. Unfortunately, most users won’t read a lot of upfront instructions, so you might have to offer them in a short bulleted list or through a single image that lets them grok the application’s main point in one view.

As an example, our test user who was trying to order a custom-tailored shirt was highly confused when the first screen in Hamilton Shirts’ “Create Your Shirt” process displayed a fully designed shirt with an “Add to Bag” button. This screen mixed two metaphors: a configurator and an e-commerce product screen.

This is a case where a default value isn’t helpful: people who want to design their own shirt are unlikely to want to buy a pre-designed shirt on the first screen.

(This screen also suffers from Mistake #1: non-standard GUI controls. In addition to its non-standard drop-down selection menus in a tabbed dialog that doesn’t look enough like tabs, the screen has a non-standard way of paging through additional fabric swatches. Users are less likely to understand how to select fabrics when the controls are presented in this manner.) Our test user never understood the process of designing his own shirt on this site and ultimately took his business elsewhere.

9. Not Indicating How Info Will Be Used
The worst instance of forcing users through a workflow without making the outcome clear is worth singling out as a separate mistake: Asking users to enter information without telling them what you’ll use it for.

A classic example is the “nickname” field in the registration process for a bulletin board application. Many users don’t realize the nickname will be used to identify them in their postings for the rest of eternity — so they often enter something inappropriate.

As another example, we once tested an e-commerce site that smacked users with a demand for their ZIP code before they could view product pages. This was a big turn-off and many users left the site due to privacy concerns. People hate snoopy sites. An alternative design worked much better: It explained that the site needed to know the user’s location so it could state shipping charges for the very heavy products in question.

10. System-Centric Features
Too many applications expose their dirty laundry, offering features that reflect the system’s internal view of the data rather than users’ understanding of the problem space.

In our current study, one user wanted to reallocate her retirement savings among various investments offered by her company’s plan (for example, to invest more in bonds and less in stocks). She thought she did this correctly, but in fact she had changed only the allocation of future additions to her retirement account. Her existing investments remained unchanged. As far as the mutual funds company is concerned, new investments and current investments are treated differently. Reallocating future additions means changing the funds they’ll buy when the employer transfers money into the account. Reallocating current investments means selling some of the holdings in existing mutual funds and using the proceeds to buy into other funds.

The key insights here? Our test user didn’t have this distinction between new and old money; she simply wanted her retirement savings allocated according to her revised investment strategy.

Even users who understand the distinction between new and old money might prefer to treat their retirement savings as a single unit rather than make separate decisions (and issue separate commands) for the new and old money. It would probably be better to offer a prominent feature for changing the entire account’s allocation, and use progressive disclosure to reveal expert settings for users who want to make the more detailed distinction between the two classes of money.

Bonus Mistake: Reset Button on Web Forms
This mistake relates to Web forms, but because so many applications are rich in forms, I’ll mention it here: It’s almost always wrong to have a Reset button on a Web form.

The reset button clears the user’s entire input and returns the form to its pristine state. Users would want that only if they’re repeatedly completing the same form with completely different data, which almost never happens on websites. (Call center operators are a different matter.) Making it easy for users to destroy their work in a single click violates one of the most basic usability principles, which is to respect and protect the user’s work at almost any cost. (That’s why you need confirmation dialogs for the most destructive actions.)