All entries of my technical and business blog

The other day, I saw some 404 errors for the file IEStandards.xml in my error logs. After a little research, I found some links here and here that lead me to believe that I had done something wrong. Let me explain…

When creating a docblock in Eclipse PDT, if commenting is enabled, a template is inserted. This template references the $user variable which is usually set to whichever user you are logged into your machine with. You can change this variable on the command line every time you launch Eclipse if you really wanted to:

More and more people are requesting that their passwords not be masked - or that they have the option to toggle them. If the visitor is using Firefox, this has been a relatively easy feat. Simply add a checkbox and change the input type on click. However, in “secure” browsers like IE, yes the security of Internet Explorer, won’t allow you to do this.

So, if you’re not familiar with CSRF, check out this blog post about AJAX Security. Some of the steps talking about Cross Site Request Forgeries will help you understand the problem.

When running YSlow the other day, I was reminded that I was loading 2 stylesheets when only one would suffice. So, let this be a reminder to you - and a quick excerpt at my own solution:

I used to think that I had to remove the WWW from my URL’s to stop having duplicate content. For example, if my website The Better Bachelor were to respond at both www.thebetterbachelor.com and thebetterbachelor.com, it used to be thought that this duplicate content would lower your search result quality. This would result in duplicate content.

For many events, roughly 80% of the effect comes from 20% of the cause.

I get a few questions here and there about the location detection on whatscloseto.me. Sometimes it seems really near - other times it seems way off.

A nice free open source alternative to Crazy Egg is ClickHeat. One of my clients wanted this implemented but didn’t want to have to log in again using different criteria. I looked at the code and saw it was surprisingly easy to edit to allow a different authentication method. Let’s check it out:

When developing an application, there are usually various different environments that you run the code in. First is the development environment. Next, you have the QA or test environment, staging, and then live or production. It stands to reason that if you are using outgoing e-mail in your application, and your application is in production, it should send to the proper recipients. However, what do you do in testing and development?