November 2006 Blog Posts
To enable windows authentication on your domain.1. Open Firefox2. Navigate to the url about:config3. Locate the following preference names and put as the value the comma separated values of the address roots.network.automatic-ntlm-auth.trusted-urisnetwork.negotiate-auth.delegation-urisnetwork.negotiate-auth.trusted-urisYour value should look something like this: localhost,server1,server2,serverX
You can read his latest post here, go ahead, I'll wait.http://www.joelonsoftware.com/items/2006/11/10b.htmlWhile Joel is absolutely right about his observations on bad metrics, not having any metrics at all is just as sinful. Yes, you can have metrics in development/knowledge worker positions. Yes, crafting them is more difficult than in a factory situation where you can just count the number of widgets worker x produces. Yes, if you don't match metrics to organizational goals you can get workers abusing them and actually hurting the company instead of helping (number of lines of code anyone?).This is why you need good management in place...
One thing that I don't see enough of in job ads in my opinion is requests for developers with specific domain experience. Quite often I just see generic "junior/senior C# developer with ASP .NET" postings and then when you dig into who the hiring company is they are in a very specific industry like insurance or health care.Industry specific domains can gain a lot by hiring developers that already have work experience in them. For one, they're already familiar with the terminology they need to effectively communicate with end users. In addition, in a world where developers have a lot...
Developer metrics are hard. We all know this. Development is part science, part logic, and part creativity. As such, it is difficult to measure how well your developers are doing their jobs. Personally, on my teams I tend to manage by results. If the releases are on time and of sufficient quality, I'm a pretty happy guy. How do I measure quality, you ask? Well I'm about to show you how I've done it on teams I'm leading.I'm pretty big on developers caring about doing some of their own Q/A. Even when you have a testing team available, it's no excuse...
One question that seems to consistently bother people is how they should respond to the "salary history" question in pre-screening and interviews. I for one, refuse to ask this question, because:1. Previous salary has nothing to do with potential salary, and has very little to do with what is fair for the current position.2. Frankly, since an employer is rarely up front about posting what their willing to pay for a position, it's none of their business about how much you used to make.Regardless, many employers ask anyways, and depending on the situation here is how I respond:Pre-screening: This is...
Having been going through a lot of hiring lately at the company I work for, I have been once again been observing the behavior of candidates when interviewing for tech jobs. I have posted on this before, but it bears repeating:When you are interviewing, and they ask for your salary requirements. BE HONEST. If you give a range, and the employer makes you an offer within that range, they expect you not to come back and ask for 10-15% more now that you've "hooked them".If you can't give an honest answer about your salary requirements, how can I ever trust...